Financial transaction systems and methods utilizing a multi-reader transaction terminal

ABSTRACT

A multi-reader terminal including a magnetic stripe reader, an embossed character reader, and a magnetic ink character recognition (MICR) check reader, in an integrated stand-alone unit. The terminal is operative for gathering credit card or check information required for customer transactions at the point of sale. The terminal provides a single card passageway for receiving a credit card having a magnetic stripe and embossed characters. The magnetic stripe reader and embossed character reader read the credit card as it travels in the passageway. The embossed character reader may be selectively retracted from the card passageway. The terminal includes a plurality of serial communications ports that allow the terminal to be connected in series between a host computer and an electronic cash register. The serial ports allow connection of a signature capture pad, a personal identification number (PIN) pad, and other serial devices. The terminal is operative to intercept and respond to serial data, or to reroute serial data between any of the serial ports. The terminal is especially suitable for use in a system wherein chargeback protection is to be afforded to certain transactions in the event that information from the embossing, magnetic stripe, or MICR reader are combined with other transaction information and forwarded electronically to a transaction processor or guarantor.

CROSS REFERENCE TO RELATED APPLICATION

This application is a division of application Ser. No. 07/968,967, filedOct. 30, 1992, entitled MULTI-READER TRANSACTION TERMINAL, nowabandoned.

TECHNICAL FIELD

The present invention relates generally to financial transactionterminals, and more particularly relates to a transaction terminal thatreads account data from a credit card using a magnetic stripe reader andan embossed character reader, and also reads account data from a bankcheck using a magnetic ink character recognition (MICR) reader.

BACKGROUND OF THE INVENTION

American consumers have long been able to pay for many goods andservices with non-cash forms of payment such as checks, credit cards,and debit cards. In recent years, consumers have increasingly relied onthese non-cash forms of payment to pay for their purchases. For example,American consumers used credit cards to spend in excess of $250 billionduring 1991. During the same period, merchants accepted checks totalingmany other billions.

In many cases, merchants prefer to be paid in cash since non-cashalternatives carry some risk of non-payment. This risk includes lossesresulting from errors and from fraudulently tendered checks and creditcards. Non-cash forms of payment, particularly credit cards, also causethe merchant to incur additional expenses in the form of processingand/or handling fees.

Many merchants have found that the additional sales generated by theiracceptance of checks and credit cards outweigh the associated risks andexpenses. Consequently, the financial industry has concentrated onsystems and methods for reducing the risk of loss in spite of the everincreasing volume of non-cash transactions. Generally, a merchant's riskof loss is reduced by automatically acquiring transaction data and bypre-authorizing or verifying each transaction prior to its completion.The automatic acquisition of transaction data also reduces the amount oftime necessary to complete a transaction.

The automatic collection of transaction data reduces the risk of loss byreducing the likelihood of errors in the recording of the account numberand in other transaction data. Checks and credit cards both includeelements that facilitate the automatic collection of-account data.Checks have account information primed along their bottom edge. Thisdata is printed with magnetic ink that is read by magnetic ink characterrecognition ("MICR") machines operated by banks and other checktransaction processors. Credit cards typically provide account data intwo forms: characters embossed on the face of the card that indicate thename of the cardholder, the account number, and an expiration date; anda magnetic stripe on the back of the card that contains the accountnumber, expiration date and other information.

Pre-authorization or verification of each transaction usually reduces amerchant's risk of loss by passing it to a third party or transactionguarantor. Third party transaction guarantors contract with the merchantto provide credit card or check authorization services. Thesetransaction guarantors, sometimes associated with financial transactionprocessors, operate computer systems and communication networks foracquiring proposed transaction data from merchants, looking up creditcard and checking account numbers in databases, and providingauthorizations or warnings to the merchants.

In these transaction guarantor systems, a merchant provides proposedtransaction data to the transaction guarantor prior to the completion ofthe transaction. The transaction guarantor then verifies the purchaser'savailability of bank funds or credit. If the transaction guarantor issatisfied that the merchant's customer has sufficient funds or availablecredit, the transaction guarantor will authorize the transaction, andwill absorb the loss in the event the payment is uncollectible. Systemsused by transaction guarantors to gather and verify transaction data aresometimes called "chargeback protection" systems because they enable thetransaction guarantor to prevent the transaction from being "chargedback" to the merchant by a credit card issuer in the event that thetransaction was not properly authorized by the card issuer. One exampleof such a chargeback protection system is described in copending U.S.patent application Ser. No. 07/819,327, filed Jan. 10, 1992, entitled"Systems and Methods for Operating Data Card Terminals for TransactionChargeback Protection", the disclosure of which is incorporated hereinby reference and made a part hereof. (The foregoing application willhereinafter be referred to as the "Chargeback Protection Application" .)

In cases where a transaction guarantor provides authorization servicesand absorbs the risk of loss, the transaction guarantor typicallycharges the merchant a fee for these services. This fee is sometimesreduced if the merchant utilizes special data collection terminals thatautomatically collect the account data from a credit card. One exampleof a data collection terminal used in such transaction authorizationsystems is described in copending U.S. patent application Ser. No.07/820,401, filed Jan. 10, 1992, entitled "Dam Card Terminal WithEmbossed Character Reader and Signature Capture", assigned to the sameassignee as the present invention, the disclosure of which isincorporated herein by reference and made a part hereof. (The foregoingapplication will hereinafter be referred to as the "Data Card TerminalApplication".)

As previously mentioned, check processors generally utilize magnetic inkcharacter recognition ("MICR") readers to facilitate check transactionprocessing. Bank-operated MICR readers are often large and handle largevolumes of checks at high speed. Smaller versions of MICR readers,useful in point of sale or "POS" terminals or cash registers, are alsoknown in the art. An exemplary point of sale sized MICR reader isavailable from Mag-Tek, Inc. of Carson, Calif. MICR readers expeditecheck-based transactions by automatically reading the account numberfrom the magnetic ink on the check. This allows information to beprovided to a check verification service quicker and more accuratelythan when the account number is read-manually by the merchant.

Merchants that accept credit cards on a regular basis often employelectronic terminals that are able to read the account data from thecard's magnetic stripe. With these magnetic stripe or "card swipe"terminals, a merchant swipes the credit card through a slot, and theterminal automatically reads and decodes the account number andexpiration date from the card's magnetic stripe. The terminal thenprompts the merchant to enter the purchase amount. Once the data isacquired, the terminal automatically places a call to a host computer,transmits the transaction data to the host computer via modem, anddisplays the authorization code received from the host computer.Examples of such terminals are found in copending U.S. application Ser.No. 07/790,658, filed Nov. 8, 1991, entitled "Card TransactionTerminal", and in the referenced Data Card Terminal Application, bothassigned to the same assignee of the present application. U.S. Pat. No.4,788,420 to Chang et al. also describes a magnetic stripe card swipeterminal.

Industry data indicates that a credit card's magnetic stripe isunreadable in approximately eight (8%) percent of credit cardtransactions. This situation occurs when the magnetic stripe has beendamaged or intentionally destroyed. In cases where the magnetic stripeis unreadable, the merchant must read the account number and expirationdate from the embossed characters on the card and enter the accountnumber via the terminal's keypad. As a result, the advantages ofautomated data entry are lost (e.g., the risk of error is increased).Moreover, some transaction guarantors will not provide chargebackprotection for transactions where the account number cannot be read fromthe credit card, since an unreadable magnetic stripe can be anindication of fraud or tampering.

In cases where the magnetic stripe is damaged but the card is otherwisevalid and unaltered, it would be desirable to automatically read anddecode the account number from the credit card's embossed characters. Ifthe embossed account number can be read automatically, the chances oferror are reduced. One example of an embossed character reader suitablefor use in credit card transaction terminals is disclosed in U.S. patentapplication Ser. No. 07/910,410, filed Oct. 30, 1992, entitled "EmbossedCard Reader", now abandonded, and assigned to the same assignee as thepresent application, the disclosure of which is incorporated herein byreference and made a part hereof. (The foregoing application willhereinafter be referred to as the "Embossed Character ReaderApplication".)

Many merchants have significant investments in POS terminals orelectronic cash registers. Sometimes, these POS terminals are connectedto a merchant's accounting computer system or "in-store processor" via adata communications network, to facilitate the merchant's businessoperations. In order to facilitate the automatic collection oftransaction data, it would be desirable to provide a transaction dataterminal that could be used in conjunction with existing electronic cashregisters and POS terminals. Since mass merchandisers often have manypoint of sale terminals within one store, and only a limited amount ofcounter space is available for each terminal, it is desirable that anytransaction data terminal be compact and inexpensive. In addition, it isnecessary for these terminals to operate in an environment where thepoint of sale terminal is connected to the merchant's host computer.

Accordingly, there is a need for a compact and inexpensive combinationcheck reader, a magnetic stripe reader, and an embossed character readerthat can be connected to existing point of sale equipment and operatedtogether with the merchant's existing in-store processor. Prior to thepresent invention, such terminals have not been known.

Therefore, there is a need for a multi-reader terminal that integrates amagnetic ink character recognition reader, an embossed character reader,and a magnetic stripe reader into a compact point-of-sale terminal.Furthermore, the multi-reader terminal should be able to be connected toexisting point of sale terminals and provide the data in a format thatis required by the terminal.

SUMMARY OF THE INVENTION

The present invention is a multi-reader terminal apparatus operative togather credit card and/or check information necessary for customertransactions such as sales, refunds, etc. at the point of sale. In orderto accomplish this, the preferred multi-reader terminal is particularlysuitable for connection to a merchant's existing point of saleelectronic cash register or terminal. The multireader terminal isequipped with a magnetic stripe reader, an embossed character reader,and a MICR check reader, and adds these functionalities at the point ofsale. In addition, the preferred apparatus supports a signature capturepad, a PIN pad, and possibly other serial devices to be controlledthrough one of a plurality of serial interfaces. The preferred magneticstripe reader and embossed character reader are combined into a single,compact card reader subassembly that is operative to attempt to read themagnetic stripe on an inserted credit card one or more times, and undercertain conditions read the embossing on the card to obtain the accountnumber on the card.

Utilizing these multiple readers, the multi-reader terminal is able toobtain all of the information necessary for the optional chargebackprotection services offered by certain transaction guarantors. Most ofthe special logic required for chargeback protection is handledinternally by the multireader, associated with the transaction data, andprovided as a data output to a transaction processor or guarantor. As aresult of the internal credit card validation routines built into themulti-reader, chargeback protection can be implemented with minimalprogramming changes to existing point of sale (POS) systems and in-storeprocessors.

The majority of the commands and features of the multi-reader operate ina fashion consistent with most other computer peripherals, i.e. acontrolling system such as a POS cash register or in-store processorissues a command, and the peripheral performs the required task. Forexample, the preferred multi-reader may be connected to an electroniccash register to operate in response to commands from the cash register,or the multi-reader may be connected in series between an in-storeprocessor and a dumb POS terminal. The multi-reader is operative torespond to commands directed to it, and if connected in between anin-store processor and a dumb terminal, it will recognize commandsdirected to it but will pass through commands and data intended ascommunications between the in-store processor and the POS terminal.

Under certain conditions, the multi-reader requests the use of a displayand keyboard of the POS system for this task. When the multi-readerreceives a command to get credit card data, it will attempt to gatherall data required for credit approval from an inserted credit card(using the rules of chargeback protection if this feature is enabled forthe card in question). If necessary, the multi-reader sends data packetsto the POS system requesting that it display messages or obtain keyboardinput from the user.

When the multi-reader is idle, it is waiting to receive commands from aconnected POS system. Depending on the configuration, the magneticstripe reader, the embossed character reader, and check MICR reader maybe enabled while in this idle state. An enabled reader can be activatedby inserting a card or check. When a command is received or a reader isactivated, all unrelated input devices are disabled until the command orthe data from the activated reader is processed. Activating a readerplaces the multireader in the relevant mode (i.e. inserting a card intothe swipe reader is equivalent to the POS system sending themulti-reader a command to get the credit card data and then the userinserting a card).

Briefly described, the multireader terminal of the present invention isable to perform the above-described functions by incorporating amagnetic ink character recognition reader, magnetic stripe reader,embossed character reader, and data ports into a single terminal. Thedata ports include a plurality of individually configurable serialcommunications ports that can be connected to a host computer system,cash register, and other serial data peripheral devices. To workeffectively, the terminal is capable of intercepting and responding toserial data intended for the terminal, and to reroute serial dataintended for one of the other serial devices.

More particularly described, a multireader terminal constructedaccording to the present invention includes a housing and card transportmeans. The housing defines a card passageway for receiving the card. Themagnetic stripe reader and embossed character reader are positioned toengage the card as it is transported along the passageway.

The preferred housing includes a top portion and a bottom portion. Thetop and bottom portions together define the card passageway. The cardtransporting means includes a plurality of drive rollers, and a motorconnected to the drive rollers. The drive rollers are partially disposedwithin the passageway and operative to engage the card. In order toreduce friction between a card and the top portion of the housing, thepreferred housing top portion defines a plurality of card support ribs.The housing bottom portion includes biasing means for biasing the cardagainst the embossed character reader during a read cycle.

According to another aspect of the present invention, the embossedcharacter reader may be selectively positioned to engage the card, orretracted from the card passageway. The preferred multireader terminalincludes a read head positioned to extend through an opening in the tophousing into operative proximity to the embossed on a card as it istransported therethrough. The selective embossed character positioningmeans includes an electrical actuator operative to move the read headinto the operative proximity with the card.

According to another aspect of the present invention, the multi-readerterminal is response to a programmable internal security indicator suchas a "high risk" flag. If the security indicator is set, the preferredterminal reads card data from both first and second card identifyinginformation readers, such as an embossed character reader and a magneticstripe reader for a credit card, and compares the data received fromeach. If the card identifying data corresponds to each other, theterminal provides verified card identifying information via outputmeans. If the security indicator is not set, the terminal provides cardidentifying data from either of the card identifying informationreaders. In the preferred terminal, the card identifying information isthe account number, and the first and second card identifyinginformation readers are the magnetic stripe reader and embossedcharacter reader, respectively.

According to another aspect of the present invention, the multireaderemploys a method of obtaining and providing card identifying informationfrom a data card presented in connection with a financial transactionwhere the data card has a magnetic stripe and an embossed regioncontaining identifying information. The method includes the steps ofreading the magnetic stripe to obtain magnetic stripe card identifyinginformation, and determining whether the magnetic stripe cardidentifying information is valid. If the magnetic stripe cardidentifying information is invalid, the method reads an embossed regionon the data card to obtain embossed card identifying information.

More particularly described, the preferred method, in response to themagnetic stripe card identifying information being invalid, restores theinvalid magnetic stripe card identifying information with at least aportion of the embossed character card identifying information to obtainrestored magnetic stripe card identifying information. The cardidentifying information including valid magnetic stripe card identifyinginformation, restored magnetic stripe card identifying information, orembossed card identifying information is provided to a host computer. Inthe preferred terminal, the card identifying information includes thecard account number. The preferred method is operative to restoremagnetic stripe data from track 1 with data from track 2, or vice versa.In addition, it is possible to restore magnetic stripe data from eithertrack with data from the embossed character reader.

According to another aspect of the present invention, there is provideda financial transaction processing system for acquiring transaction dataassociated with a financial transaction. The system of the presentinvention includes a host computer, at least one electronic cashregister operative for acquiring predetermined transaction informationand for communicating the transaction information to the host computer.The system also includes communication means for transferringtransactional information between the host computer and the electroniccash register, and at least one multi-reader terminal independent of theelectronic cash register. The multireader terminal is operative toacquire additional transaction information in connection with thefinancial transaction. The various means of obtaining transactioninformation include a keypad associated with the electronic cashregister, an embossed character reader, a magnetic stripe reader, and amagnetic ink character recognition reader. The transaction data mayinclude transaction amount, credit card account number, and checkingaccount number.

More particularly described, the preferred system includes a serial datacommunications link between the host computer and the electronic cashregister where the multireader terminal connected between the electroniccash register and the host computer by means of first and secondcommunications links. The multi-reader terminal is operative to respondto a predetermined set of signals from the host computer on the firstcommunications link, and to pass signals intended for the electroniccash register to the electronic cash register via the secondcommunications link. The multi-reader terminal is also operative to passsignals from the electronic cash register on the second communicationslink to the host computer on the first communications link.

In the preferred system, the multireader terminal is selectivelyoperative to: ignore all incoming data received on an incoming serialport; accept all incoming data received on an incoming serial port asintended for the second transaction terminal; redirect all incoming datareceived on an incoming serial port, except for data recognizable asintended for the second transaction terminal to an outgoing serial port;unconditionally redirect data received on an incoming serial port to aselected outgoing serial port with no regard to the format and substanceof the data; or communicating with a peripheral device connected to aselected serial port.

According to another aspect of the present invention, there is provideda method of operating an adjunct transaction terminal in conjunctionwith a system having a host computer and an electronic cash register.The adjunct transaction terminal is connected for data communicationsbetween the host computer and the electronic cash register. The methodincludes the following steps: providing an adjunct terminal foracquiring adjunct transaction information independently of theelectronic cash register; connecting the adjunct terminal forcommunications in series between the host computer and the electroniccash register; receiving signals between the host computer and theelectronic cash register; determining the intended destination of thesignals; responding to predetermined signals intended for the adjunctterminal by performing functions associated with the adjunct terminal;and forwarding remaining signals to their intended destination.

Accordingly, it is an object of the present invention to provide acombination magnetic ink character recognition reader for checks,embossed character reader for credit cards, and magnetic stripe readerfor credit cards.

It is another object of the present invention to provide a combinationcheck and credit card reader that is operative with existing POSequipment and in store processors.

It is another object of the present invention to provide a credit cardand check data collection terminal that is usable in conjunction withexisting data communications networks.

It is another object of the present invention to provide a combinationcheck and credit card data collection terminal that has a plurality ofdata communications ports that facilitate connection between existingPOS equipment and in-store processors, by providing capability ofdistinguishing commands and data intended as communications between theexisting POS equipment and in-store processor and directing suchcommunications properly.

It is another object of the present invention to provide a combinationcheck and credit card data collection terminal for use in conjunctionwith existing POS equipment that only has a limited number ofcommunications ports, with minimal software modifications to thein-store processor computer programs.

It is another object of the present invention to provide a combinationmagnetic stripe reader and embossed character reader for credit cardsthat is operative to read both the magnetic stripe and the embossing ona card in a single operation.

It is another object of the present invention to provide a combinationmagnetic stripe reader and embossed character reader for credit cardsthat is operative to read a credit card's account number from both themagnetic stripe and the embossing on a card and compare the numbers, toprovide additional antifraud protection and transaction verification.

It is another object of the present invention to provide a combinationcredit card and check data collection. terminal for use at the point ofsale together with existing POS electronic cash registers and terminalsthat facilitates the provision of chargeback protection services by atransaction guarantor.

It is another object of the present invention to provide a combinationcredit card and check data collection terminal that automaticallyacquires data from a credit card or check, validates same, andassociates the validated data with transaction data for purposes offacilitating the provision of chargeback protection services by atransaction guarantor.

It is another object of the present invention to provide a credit cardand check data collection terminal that is compact and inexpensive tomanufacture.

These and other objects, features, and advantages of the presentinvention may be more clearly understood and appreciated from a reviewof the following detailed description of the preferred embodiments andby reference to the appended drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. I is a perspective view of a multi-reader terminal constructed inaccordance with the preferred embodiment of the present invention forreading transaction data from checks and credit cards.

FIGS. 2A-2C are block diagrams illustrating a variety of systemconfigurations in which the preferred multi-reader terminal of FIG. 1may be used.

FIG. 3 is an exploded perspective of the multi-reader terminal of FIG.1, showing the magnetic ink character recognition reader and credit cardreader subassemblies.

FIG. 4 is a bottom perspective or "worm's eye" view of the credit cardreader subassembly in the preferred multi-reader terminal.

FIG. 5 is a left side view of the preferred multi-reader terminalshowing the magnetic ink character recognition reader and credit cardreader subassemblies.

FIG. 6 is a right side view of the preferred multi-reader terminalshowing the magnetic ink character recognition reader and credit cardreader subassemblies.

FIG. 7 is a top view of the preferred multi-reader terminal.

FIG. 8 is a front view of the multi-reader terminal.

FIG. 9 is a rear view of the multi-reader terminal.

FIG. 10, consisting of FIGS. 10A and 10B, is an exploded perspectiveview of the credit card reader subassembly.

FIG. 11, consisting. Of FIGS. 11A-11H, is a cross-sectional view takenalong the lines 11--11 of FIG. 7, showing the movement of a credit cardthrough the reader during a read cycle.

FIG. 12 is a bottom plan view of the top portion of the credit cardreader housing.

FIG. 13 top plan view of the bottom portion of the credit card readerhousing.

FIG. 14 is a cross-sectional view taken along the line 14--14 of FIG. 7.

FIG. 15 is a block diagrammatic representation of the electroniccircuitry employed in the preferred multi-reader terminal.

FIG. 16 is a flow diagram illustrating the main loop of the operation ofa terminal constructed in accordance with the present invention,implemented as computer software.

FIG. 17 is flow diagram illustrating the preferred GET CREDIT CARD DATAsubroutine forming a part of the terminal software method of FIG. 16.

FIG. 18 is a flow diagram illustrating the preferred READ CARD DATAsubroutine forming a part of the get credit card data subroutine of FIG.17.

FIG. 19 is a flow diagram illustrating the preferred HIGH RISK CARD DATAsubroutine forming a part of the terminal software method of FIG. 17.

FIG. 20 is a flow diagram illustrating the preferred GET CHECK MICR DATAsubroutine forming a part of the terminal software method of FIG. 16.

FIG. 21 is a flow diagram illustrating the preferred GET PIN subroutineforming a part of the terminal software method of FIG. 16.

FIG. 22 is a flow diagram illustrating the preferred GET SIGNATUREsubroutine forming a part of the terminal software method of FIG. 16.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Referring now to the drawings, in which like numerals represent likeelements throughout the several figures, FIG. 1 shows a multi-readerterminal 10 constructed in accordance with the present invention. Thepreferred multi-reader terminal 10 is designed to gather all credit cardor check information necessary for customer transactions such as salesand refunds. Therefore, the terminal 10 is operative to read accountdata from a check 15 or a credit card 20. When reading data from a check15, the multi-reader terminal 10 reads account data from the magneticink characters 25 printed along the bottom edge of the check. Whenreading a credit card 20, the multi-reader terminal 10 reads accountdata from the magnetic stripe 30 on the back of the credit card, or fromthe embossed characters 35 on the front of the card.

The multi-reader terminal 10 includes a magnetic ink characterrecognition ("MICR") reader 51, positioned on the top of the terminal.The MICR reader 51 is concealed by a top outer cover 40 and a top centercover 45. Together, the outer cover 40 and center cover 45 form a MICRslot 50 that directs the check 15 into and through the MICR reader 51.When the check 15 is inserted into MICR slot 50, the check is drivenpast a read head in the MICR reader 51 that reads the account numberfrom the magnetic ink characters 25 printed along the bottom edge of thecheck 15. The position of the characters 25 along the bottom edge of thecheck is governed by ANSI standard X9.13-1990, and the form or font ofthe characters is governed by ANSI standard X9.27-1988, which arepublished by the American National Standards Institute, Inc., 1430Broadway, New York, N.Y., and are incorporated herein by reference. Theoperation of the MICR reader 51 is described more completely below.

The multi-reader terminal 10 also includes a card reader (not shown),positioned interiorly of a card slot 60, that is capable of reading boththe magnetic stripe 30 and embossed characters 35 on credit card 20. Themagnetic stripe 30 and embossed characters 35 are governed by ANSIstandards X4.16-1983 and X4.13-1983, respectively, which are publishedby the American National Standards Institute, Inc., 1430 Broadway, NewYork, N.Y., and are incorporated herein by reference. The card reader isconcealed by the bottom cover 55, and is accessed by means of the cardslot 60. In the preferred terminal 10, the card slot 60 is located onthe front panel immediately below the intersection of the top centercover 45 and the bottom cover 55. The operation of the card reader isdescribed more completely below.

The terminal 10 provides, on its exterior housing 55, a plurality ofserial data communications ports 62 for providing data communicationsbetween control circuitry contained within the terminals and externaldevices. In the preferred embodiment, four serial ports 62a-62d areprovided. These serial ports are bidirectional and are operative in themanner described herein to allow connection in between existing POSterminals and/or electronic cash registers, and in-store processors.

System Configurations

Using the serial ports 62 for data communications, the preferredmulti-reader terminal 10 provides check and credit card readingcapabilities that may be used in conjunction with a merchant's existingpoint-of-sale ("POS") system. FIGS. 2A-2C illustrate exemplaryconfigurations in which the multi-reader terminal 10 may be used, withvarious peripheral devices connected to the terminal via the serialports 62. Those skilled in the art will understand that the hardwareconfigurations described in conjunction with FIGS. 2A-2C are providedfor purposes of illustration only and are in no way intended to restrictthe systems in which the preferred multi-reader terminal 10 may be used.

FIG. 2A illustrates the connection between a multi-reader terminal 10and a single, stand-alone electronic cash register 65. The cash register65 contemplated in FIG. 2A is capable of communicating with otherperipherals (such as a receipt printer, not shown) and may be programmedto interface with multi-reader terminal 10. Typically, an electroniccash register 65 includes a keyboard 70, a display 75, and a cash drawer80. Cash register 65 may also include a modem (not shown) and thereforebe able to communicate electronically with remote facilities such ascredit card and check authorization services via telephone line 85. Thecash register 65 and multi-reader terminal 10 are connected to eachother by means of a serial cable 90 connected to a serial port on thecash register and one of the serial port 62 on the terminal.

When used with the disclosed multi-reader terminal 10, the cash register65 may effectively be connected to a variety of peripheral devices thatfacilitate the automatic collection of financial transaction data. Forexample, the multi-reader terminal 10 may be connected via one of theserial ports 62 to a signature capture pad 95, which is operative todigitize a customer's signature when collected in conjunction with atransaction such as a credit card purchase. Once the signature isdigitized, the signature may be transmitted through the terminal 10, tothe cash register 65, and then via data communications, means associatedwith the cash register to a third-party credit card processor, alongwith other transaction data, where the data may be stored for futurereference. The preferred signature capture pad includes a signaturecapture window 100 and an electronic stylus 105. A signature capturedevice operative as the signature capture pad 95 is described in thereferenced Data Card Terminal Application.

The multi-reader terminal 10 may also be connected to a personalidentification number ("PIN") pad 110 via one of the serial ports 62. APIN pad typically includes a keypad 115 and a display 120, and is oftenused in conjunction with debit card transactions. The PIN pad allows thecardholder to secretly enter his or her PIN. In this manner, thecardholder's identity is verified and the transaction is completed. Asused herein, the term "credit card" is also intended to include debitcards to the extent account data is provided in the form of a magneticstripe and embossed characters.

FIG. 2B illustrates a second exemplary configuration in which themulti-reader terminal 10 may be used. As in FIG. 2A, a serial port 62 onthe multi-reader terminal is connected to a serial port on electroniccash register 65 by means of a serial data cable 90. However, theelectronic cash register 65 in FIG. 2B is connected to a host computer125 via a data communications network cable 130. The host computer 125provides means for communicating with remote facilities such as creditcard and check authorization services via telephone line 85. As in FIG.2A, the multi-reader terminal 10 may alternatively be connected to asignature capture pad 95 and a PIN pad 110, through other serial ports.

The types of electronic cash registers 65 shown in FIG. 2B as connectedto a host computer 125 are often "smart" enough (that is, containsufficient data processing power internally) to operate independently ofthe host computer. Such smart cash registers typically communicatetransaction data between the cash register and the host computer, andare considered "stand alone". However, other types of cash registers are"dumb" terminals, that is, they require constant communication andcontrol by an in-store processor ("ISP").

Some dumb POS terminals 140 are equipped with only one serial port,which is intended for direct connection to a controlling ISP. These dumbterminals (or for that matter, any terminals with only one or a few datacommunications ports) cannot normally be connected to other peripheraldevices at the point of sale, because they only have a limited number ofdata communications ports. However, limited-port terminals, dumb orotherwise, can be connected to a number of peripheral devices at thepoint of sale with use of the present invention.

FIG. 2C illustrates a multi-reader terminal 10 connected in seriesbetween an ISP 135 and a dumb POS terminal 140. In this configuration,it is contemplated that the POS terminal 140 is not independentlyprogrammable and cannot operate on a stand-alone basis, but must becontrolled by the ISP 135. In this series configuration, themulti-reader terminal 10 is connected to the ISP 135 by a cable 130'running between a serial port on the ISP 135 and one of the serial ports62 on the multi-reader terminal. Another of the multi-reader terminal'sserial ports 6:1 is used to connect the multi-reader terminal to the POSterminal 140 via cable 90'. The two remaining serial ports 62 may beconnected to other peripheral devices, such as a signature capture pad95 and/or a PIN pad 110.

As described in greater detail below, the serial ports 62 on themulti-reader terminal 10 may be individually configured. Therefore, itis possible to pass data from one serial port to another. In addition,the multi-reader terminal 10 may be programmed to monitor data from theISP 135 and to distinguish data intended for the POS terminal 140 fromthat intended for the multi-reader terminal 10. The multi-readerterminal 10 responds to data intended for it, and passes other data onto the POS terminal. Likewise, data transmitted from the POS terminal140 to the ISP 135 is passed through the multi-reader terminal 10without interference. The operation of the multi-reader terminal 10 asit relates to its handling of serial data is described more completelybelow.

Multi-Reader Mechanical Structure

Turning now to FIG. 3 for a discussion of an exploded perspective viewof the major subassemblies that make up the preferred multi-readerterminal 10. The terminal 10 includes a magnetic ink characterrecognition ("MICR") reader 51 as one subassembly and a credit cardreader 155 as another subassembly. Both are mounted to a base plate 160and are concealed by the top outer cover 40, top center cover 45, andbottom cover 55. The top outer cover 40 and top center cover 45 togetherdefine the MICR slot 50, which forms a "U"-shaped path of travel for acheck.

The base plate 160 is supported by legs 162 inside the bottom cover 55,providing space for various mechanical and electronic components. Aprinted circuit (PC) board 163 is mounted on the floor of the bottomcover 55, supported on standoffs beneath the base plate, and isconnected by electrical cables to the various electrical components inthe multi-reader. The PC board supports various circuitry componentsdescribed herein.

The preferred credit card reader 155 is a dual function credit cardreader, automatically operative to read the magnetic stripe on aninserted credit card, as well as the embossed characters on the creditcard, and to provide data indicative of the credit card's account numberand other information. This data is provided to a communicationscontroller (described in greater detail below) that controls thetransmission of data from the terminal 10 via the serial ports.

The preferred MICR reader 51 is a model 22032001, manufactured byMag-Tek, Inc., Carson, Calif. Details of the construction and operationof the MICR reader are available in the literature provided by themanufacturer. The MICR reader also provides signals to themulti-reader's communications controller, as described below, indicativeof the magnetic ink characters primed on a check or other article. TheMICR reader is operative to read all magnetic ink characters encoded onthe check or article in the proper position, typically including bankaccount, bank identity, and, if provided, a transaction amount. It willbe understood that cash registers or other POS equipment with magneticink printers may imprint the transaction mount or other data on a checkor article, and these the printed characters may be read by the MICR.

The MICR reader 51 is attached to the base plate 160 at the end adjacentthe closed end of the outer top cover 40, and includes a flywheel 165that is driven by MICR motor 170 and MICR pulley 175. The flywheel 165,pulley 175, and motor 170 are connected by drive belts 180a, b. Themotor 170 is housed within a motor housing 190 that is also attached tobase plate 160. The flywheel 165 includes a rubber band 185 about itscircumference that engages a check and provides sufficient frictionbetween the flywheel 165 and a check 1 S. When the control circuitry(not shown) receives signals from sensors (not shown) indicating that acheck has been inserted into MICR slot 50 (see FIG. 1), the motor 170 isenergized and the check is propelled through MICR slot 50 and past aMICR read head (not shown).

Data indicative of the characters printed in magnetic ink on a check areread by the circuitry of the MICR 51, and provided to a communicationscontroller (described in greater detail below) that controls thetransmission of data from the terminal 10 via the serial ports.

FIG. 3 also illustrates the mounting of the credit card reader 155. Thecard slot 60 is defined in a card reader housing 195 that is mountedbeneath the base plate 160, at the end opposite the MICR flywheel 165.The card slot 60 extends into a passageway defined inside the cardreader housing 195 forming a path of travel for the card. A credit cardis propelled through the card slot by drive rollers 200a, b. Driverollers 200a, b are driven by card reader motor 205 that is mounted on amotor mounting bracket 207. The motor 205 and motor mounting bracket 207are mounted on the top side of base plate 160. Motor 205 drives a largepulley 210 mounted to a shaft 212 via a drive belt 215. The shaft 212extends through, and is supported by, motor housing 190, and has a smallpulley 213 mounted at the end opposite the large pulley. The pulley 210turns shaft 212 and small pulley 213, which in turn, drives driverollers 200a, b via drive belt 220. Tensioning pulley 225 is provided toadjust the tension of drive belt 220.

A motor filter printed circuit board 230 is attached to the top of motorhousing 190 and provides circuitry to condition control signals to bothmotors 170, 205.

A tubular linear actuator or solenoid 235 is mounted beneath motor 205.The solenoid 235 is operative to lower an embossed character read headinto engagement with a credit card, and to remove the read head fromengagement, as is described below in greater detail.

FIG. 4 is a bottom perspective, or "worm's eye" view of the preferredmulti-reader terminal 10. FIG. 4 also illustrates the relation betweenthe base plate 160 and the elements of the card reader mechanism. Cardreader motor 205 and mounting bracket 207 are mounted on the top of thebase plate 160. Motor 205 drives small pulley 213 via large pulley 210(not shown) and shaft 212 (not shown). The shaft extends through motorhousing 190. Motor filter printed circuit board 230 is mounted atopmotor housing 190. Leg 162 are mounted on the bottom of base plate 160.

As best seen in FIG. 4, the preferred credit card reader 155 comprises acard reader housing 195 including a transport top portion 250, atransport bottom portion 255, and a roller retainer cover 260. The cardslot 60 extends into the space defined by the transport top and bottomportions 250, 255.

The roller retainer cover 260 is fastened to the transport bottomportion 255 by screws 265 and retains the drive rollers 200a, b, forrotatable movement. The drive rollers 200 are driven by a drive belt 220that is coupled to the motor 205. A tensioning idler pulley 225 ismounted adjacent the driver roller 200a to allow adjustment of thetension of drive belt 220.

The roller retainer cover 260 also retains and operatively supports amagnetic read head (not shown) adjacent the read head slot 275 so thatthe magnetic read head operatively engages with the magnetic stripe on acard through openings (not shown in FIG. 4) leading to the card slot.

Further details of the relationship between the transport top and bottomportions 250, 255 and the roller retainer cover 260 are described morecompletely below.

FIG. 5 is a left side view of the preferred multi-reader terminal 10,without the covers. This view illustrates the base plate 160 and certaincomponents of the MICR reader 51. The MICR reader 51 includes flywheel165, rubber band 185, MICR pulley 175, MICR motor 170, and drive belts180a, b. The pulley 175 is mounted on a vertical shaft 270 that ismounted to the mounting plate 160. MICR motor 170 is housed within motorhousing 190.

FIG. 5 also illustrates portions of the card reader subassemblydescribed above in conjunction with FIGS. 3 and 4. These parts includethe card reader motor 205, which is attached to motor mounting bracket207. Motor filter printed circuit board 230 is mounted atop motorhousing 190. The motor 205 indirectly drives small pulley 213 (see FIGS.4 and 5). Small pulley 213, in turn, drives drive rollers 200a, b, bymeans of drive belt 220. Tensioning pulley 225 is used to adjust thetension on drive belt 220. Direction pulley 280 is used to alter thedirection of drive belt 220 from the vertical to the horizontal.

Drive rollers 200a, b are supported for rotatable movement by the rollerretainer cover 260, which is attached to transport bottom portion 255 byscrews 265. Transport top portion 250 fits partially within transportbottom portion 255, and both are attached to the bottom of base plate160.

Still referring to FIG. 5, the solenoid 235 is a tubular linear actuatoror solenoid configured to pull or retract upon actuation, to move anembossed character read head (not shown) into position inside the readerfor reading embossed characters. When energized, a plunger 285 is pulledpartially into the body of solenoid 235. The plunger 285 is connected tospring 290, which in turn is connected to a lever 295. The lever 295 isattached to a cam-type shaft (not shown) having a flat side, which ismounted in cam mounting blocks 305. The operation of the cam isdiscussed below in conjunction with the embossed character read headsubassembly.

The spring 290, being connected between the plunger 285 and the lever295 being acted upon, allows the plunger to seat or retract completelywhen the solenoid 235 is energized. If the plunger is seated completely,the solenoid is able to exert several pounds of force while drawing verylittle current. If the plunger does not seat complete, the solenoid willbe able to exert only a few ounces of force and will draw more current.Thus, it is desirable to allow the solenoid to pull against the springinitially until the plunger is seated. The force of the spring 290 isthen able to exert the necessary force on the lever 295 to cause theread head to move into position.

FIG. 6 is a right side view of the multi-reader terminal 10. In additionto the elements shown in FIG. 5, FIG. 6 shows a drive sprocket 310attached to the shaft of the card reader motor 205. The drive sprocket310 drives the large pulley 210 by means of a toothed drive belt 215. Inaddition to the drive sprocket 310, the motor shaft has a slotted disk315 attached thereto. The slotted disk 315 has a plurality ofequally-spaced narrow slits 320 formed about its circumference, and ismounted to rotate within the operative confines of an opticaltransmitter/receiver 325.

The slotted disk 315, together with the optical transmitter/receiver325, comprise an optical encoder 330 that is used to measure thedistance of travel of a credit card within the card slot. While anoptical encoder is employed in the preferred embodiment to measure themovement of the card within the passageway, those skilled in the artwill understand that other types of position sensors or encoders such asmagnetic pickups, optical, or magnetic sensors may also be successfullyemployed.

The optical transmitter/receiver 325 incorporates a light emitting diodeand a phototransistor that are aligned with each other. As the slotteddisk 315 rotates, the light transmitted between the light emitting diodeand the phototransistor is interrupted or pulsed. Electrical signalscorresponding to the pulsed light are provided on wires (not shown) thatare connected to the optical encoder 330. By knowing the relationshipbetween the slit spacing and the rotation of the drive rollers, amicroprocessor may calculate the distance of travel of the card.

FIG. 7 is a top plan view of the preferred multi-reader terminal 10, andshows the relationship between a credit card 20, the embossed characters38 thereon, the base plate 160, the MICR reader 51, and portions of thecard reader subassembly 155. The components of the MICR reader are shownin phantom for clarity, and includes the flywheel 165, the MICR pulley175, and the MICR motor 170.

FIG. 7 provides another view of the connections between the card readermotor 205 and drive sprocket 310. Belt 215 connects drive sprocket 310to the large pulley 210 and provides means by which motor 205 drivesshaft 212. The small pulley 213 is located on the opposite end of theshaft 212, and drives the drive belt 220. The slotted disk 315 ismounted adjacent to the drive sprocket 310.

Tubular pull solenoid 235 is mounted between the card reader motor 205and base plate 160, underneath the motor. The solenoid plunger 285extends from the solenoid and is attached to the spring 290. A read headsubassembly 350 is provided for reading the embossing on a card 20. Thesolenoid is operative to cause the embossed character read headsubassembly 350, which is normally maintained in a retracted position,to be lowered into the card slot so that it makes operative contact withthe embossed characters 35 on the credit card.

In order to lower the read head subassembly into operative position,means 340 are provided for engaging the embossed card reader subassembly350 into operative position for reading the embossing on a card beingtransported inside the reader 155. The embossed card reader engagingmeans 340 comprises a cam shaft 355 and lever 295 are connected to thesolenoid 235 via spring 290. As best seen in FIG. 10 and in FIGS. 11Eand 11F, the cam 355 is mounted in cam mounting blocks 305, and has aflat side terminating in an engaging edge 357 that is positioned overthe read head subassembly 350. The cam 355 rotates slightly when thesolenoid 205 is energized (retracted). The edge 357 of the flat portionof the cam 355 engages with the read head subassembly 350 and depressesit into operative position to read the embossing, as shown in FIG. 11F.The mounting and operation of the embossed character read headsubassembly will be described more completely below.

FIGS. 8 and 9 are a front view and rear view, respectively, of theinternal portions of the preferred multi-reader terminal 10. The topouter cover 40, top center cover 45, bottom cover 55, and MICR flywheel165 are shown in phantom for reference. The top outer cover 40 and topcenter cover 45 define the MICR slot 50, into which a check is inserted.

As seen in FIG. 8, the card reader motor 205 is attached to an uprightmotor mounting bracket 207, which is mounted on the base plate 160. Theslotted disk 315 and drive sprocket 310 are mounted on the shaft thatextends from motor 205. A portion of the slotted disk 315 is extendedinto a void formed in the horseshoe-shaped optical transmitter/receiver325. The motor 205 is operative to drive the large pulley 210 by meansof the drive belt 215. The large pulley 210 is connected to the shaft212; the small pulley 213 is mounted on the end of the shaft 212opposite the large pulley 210. The drive belt 220 is in operativecontact with small pulley 213, and is operative to drive the driverollers 200a, b.

FIG. 9, in addition to the elements described in the precedingparagraph, illustrates the position of the solenoid 235 between themotor 205 and base plate 160, and shows that the solenoid is mountedapproximately midway across the width of the base plate 160, with theembossed character reader engaging means 340 positioned offset to oneside. The lever 295 is mounted on the interior side of the cam mountingblocks 305. The cam 355 is mounted between the cam mounting blocks 305,aligned with the actuator of the solenoid 235, immediately above theread head subassembly 350. The interaction between the cam 355 and readhead subassembly 350 will be described more completely below.

FIG. 10 illustrates, in exploded form, a card reader housing comprisingthe transport top portion 250 and a transport bottom portion 255 of thecredit card reader assembly 155. Together, the top portion 250 andbottom portion 255 define a path of travel for an inserted card,beginning at the card slot 60 and extending along the length of the cardreader housing to a downwardly extending end portion 361 which formsbarrier to stop inward movement of the credit card. The card readerhousing is mounted to the bottom side of the base plate 160 (not shown).

The transport bottom portion 255 includes two transversely extendingrectangular slots 375a, b, through which portions of the surface of thedrive rollers 200a, b extend, drive rollers 200 protrude into the slots375 and make contact with a credit card once it is inserted into theslot 60. As the card is inserted into the slot, it passes through ahorseshoe-shaped optical card insertion sensor 377, which is identicalto the optical transmitter/receiver 325 that forms a part of the encoder330. The optical sensor 377 provides a signal to the control circuitry(not shown) indicating that a card has been inserted into the slot.

After detection of insertion of a card, the control circuitry thenactivates the motor 205 to begin a card read cycle. When motor 205 isactivated, the leading drive roller 200a "grabs" the card and pulls itcompletely into the slot 60. The spacing between slots 375a, b isslightly less then the length of a credit card so that the card is"handed off" from one roller 200a to the other or trailing roller 200b.

The transport bottom portion 255 also includes a magnetic read head slot380, through which magnetic stripe read head 385 protrudes intooperative contact with the magnetic stripe on a card being transported.The read head slot 380 is positioned so that the magnetic stripe on theback of a credit card passes directly over the read head as the cardtravels through the slot 60.

The transport bottom portion 255 further includes a biasing ramp 390defined on its interior bottom wall. The biasing ramp 390 extendsupwardly into the path of travel of a card, and is aligned with the pathof the embossed characters on the card. The biasing ramp is operative topress or bias the embossed characters upward against the embossedcharacter read head subassembly 350 when the read head is lowered tomake contact with the credit card. This ensures that there is properoperative contact between the embossed characters 35 and the read head350.

The preferred biasing ramp 390 comprises a flat rectangular metal springthat is confined within a rectangular depression 391 in the interiorbottom surface or wall of the transport bottom portion 255. The elongatedimension of the metal of the spring is slightly larger than theelongate dimension of the rectangular depression 391, so that the springmust be slightly bent to fit into the depression and it bows upwardslightly. Alternatively, the biasing ramp 390 may be formed as a moldedfeature of the transport bottom portion 255.

Still primarily referring to FIG. 10, the transport top portion 250includes a read head mounting recess or slot 400. The slot 400 ispositioned directly above the biasing ramp 390. An embossed characterread head subassembly 350 is received within the slot 400 and issupported upon two flat springs 405. The read head subassembly 350 isoperative to contact with the embossed characters on a card and provideelectrical signals corresponding to the characters, which are decoded asdescribed in the referenced Embossed Character Reader Application. Thepreferred read head subassembly 350 includes a plurality of elongatepins 401 that contact with the embossing on the card. In the preferredembodiment, the read head subassembly 350 is an embossed characterreader constructed in accordance with the referenced Embossed CharacterReader Application. Reference is made to this incorporated-by-referenceapplication for a discussion on the operation of this subassembly.

The embossed character read head subassembly 350 is supported in theslot 400 upon two beryllium copper springs 405 beneath cam 355 andbetween cam mounting blocks 305. The copper springs 405 support the readhead subassembly in a normally retracted or upward position, with thepins of the embossed character reader withdrawn from the path of thecard. When the engaging edge 357 of the cam 355 is not in contact withthe read head 350, the springs 405 exert upward pressure on the readhead 350 and cause the read head to be retracted from the card slot.When the solenoid 235 (not shown) is energized, the cam rotatesapproximately 20°, and the edge 357 exerts downward pressure on the readhead 350, causing the read head to be lowered to a second, operativeposition wherein the pins of the read head are disposed within thepassageway 448 and contact with the embossed characters on a creditcard. Once the solenoid 235 is de-energized, the springs 405 cause theread head 350 to return to its retracted position.

The springs 405 include mounting holes 406 that engage with downwardlyextending spring holding pins 408 on the bottom surface of the cammounting blocks 305. These pins 408 hold the springs in position. Eachspring is located in a shallow subrecess 407 that allows fullcompression or flattening when the read head is moved to its operativeposition. The springs are essentially flat beryllium copper having afirst rectangular portion 417 including the mounting holes 406 and asecond rectangular but angularly elevated portion 418. The secondangularly elevated portion 418 sits beneath the wings 232 of theembossed read head subassembly 350 and springably supports the read headin a first, normally retracted position. FIG. 14 also illustrates thissupport.

Still referring to FIG. 10, the roller retainer cover 260 supports themagnetic read head 385 and drive rollers 200a, b. The magnetic read head385 is mounted within an assembly that includes a generally rectangularleaf spring 410. The leaf spring 410 has mounting holes 415 at each endthat rest on conical mounting studs 420 defined in the cover 260. Theleaf spring 410 allows the magnetic read head 385 to float and biasesthe read head 385 upwardly through the read head slot 380 in thetransport bottom portion 255 against the magnetic stripe on a creditcard as the card moves within the slot 60. The read head slot 275 in theretainer cover 260 provides a passage for wires (not shown) that areconnected to the read head and carry electrical signals corresponding tothe account data stored on the magnetic stripe.

Each drive roller 200 is similarly constructed and comprises a generallycylindrical shaped shaft 425 having a plurality of resilient siliconerubber bushings 430 spaced apart along the shaft. The resilient bushings430, three in the preferred embodiment on each roller, provide frictionbetween the drive roller(s) and the credit card. One end of each driveroller shaft 425 includes a drive sprocket 435. The drive sprockets areengaged by the toothed drive belt 220 (not visible in FIG. 10), whichcauses the rotation of the drive rollers 200.

Each drive roller shaft 425 is supported for rotation via a pair ofneedle bearings 440 mounted at either end to reduce friction duringrotation. One bearing is spaced slightly inwardly from the drivesprockets 435, while the other is located at the opposite end of theshaft. The needle bearings 440 are supported in notches 445 formedwithin the roller retainer cover 260. The drive sprockets 440 extendbeyond the edges of the retainer cover 260, extending through an opening446 extending into the notches 445 along one side of the retainer cover.

The magnetic read head 385 and drive rollers 200a, b are held in placewithout additional fasteners when the roller retainer cover is mountedto the bottom of the transport bottom portion 255.

FIG. 11 shows the movement of a credit card 20 through the card reader155 during a read cycle. Each of the several subfigures shows a creditcard 20 having embossed characters 35 on its top surface and a magneticstripe 30 on its bottom surface. The card 20 is inserted into the cardslot 60. The top or operative surface of the magnetic stripe read head385 extends into a passageway 448 defined between the housing portions250, 255 forming the card's path of travel, and is held in place bymounting studs 420 and roller retainer cover 260. The biasing ramp 390on the transport bottom portion 255 also extends into the passageway448. The pins 401 of the embossed character read head subassembly 350are withdrawn in the rest or retracted position until the embossing isto be read.

In FIG. 11A, the credit card 20 has not yet been inserted into card slot60 and the card reader is in its idle state. In this idle state, the cam355 is positioned so that the embossed character read head 350 isretracted from the card slot 60 so as to avoid any contact with thecard. Those skilled in the art will appreciate that any contact betweenthe embossed character read head 350 and the card during a magneticstripe read cycle is likely to cause instantaneous variations in thecard's velocity and interfere with the accuracy of the magnetic striperead. Therefore, the pins 401 of the embossed character read head 350are engaged into the passageway 448 only during an embossed characterread subcycle of a card read cycle.

In FIG. 11B, the card 20 has been inserted into the card slot 60 and isin contact with the leading drive roller 200a. Immediately prior tocontacting the leading drive roller, the card encounters the card sensor377 (not shown). The card sensor 377 sends a signal to control circuitry(not shown) indicating that a card 20 has been inserted into card slot60. The control circuitry then sends signals to the motor 205 (notshown), and the motor causes drive rollers 200a, b to pull the card intothe card passageway 448.

FIG. 11C illustrates the position of the card 20 after the card has beendriven across magnetic read head 385 and into contact with drive roller200b. The drive rollers 200a, b are spaced so that the card 20 neverleaves contact with one of the rollers, but is passed or "handed off"from one drive roller to another. Thus, a card is "handed off" fromdrive roller 200a to drive roller 200b, which are rotated by a commondrive belt, and its motion is not interrupted.

As the card passes over magnetic read head 385, the reader attempts toread the account data from the magnetic stripe 30 on the bottom surfaceof the card 20. If the magnetic stripe read is successful, the card isejected as described below.

If the magnetic stripe read is not successful on the first attempt, inthe preferred embodiment the card will not be ejected until a furtherreading attempt. Rather, the card direction is reversed, and the driverollers move the card 20 back into the reader for a second magneticstripe read attempt. As the card is transported across magnetic readhead 285 for the second time, the read head attempts to read the accountdata from the magnetic stripe. Thus, in FIG. 11D the card will not beejected but will be returned into the passageway 448.

It should be understood at this juncture that the control circuitry (notshown) is operative to determine the precise position of the card 20within the passageway 448 by means of the optical encoder 330 describedabove. Thus, it is possible to stop the card in the position shown inFIG. 11D prior to its ejection, and move the card back into thepassageway for another, second attempt at reading the magnetic stripe.

If the magnetic stripe reading is successful on the second (or anysubsequent) attempt, the card 20 will be ejected from the card slot asdescribed below. If the subsequent attempt at reading is not successful,the direction of the card will be reversed again, and the card willagain be transported to the most inward position illustrated in FIG.11E. As the card 20 passes over the magnetic read head 285, anotherattempt at reading the account data recorded on the magnetic stripe ismade. If the magnetic strip read is successful on any attempt (unlessmultiple readings are required for additional security or verification),a card will be ejected as described below.

If unsuccessful at reading the magnetic stripe, the reader will keep thecard in most inward position as in FIG. 11E, while the embossedcharacter read head 350 is lowered into the passageway 448, asillustrated in FIG. 11F, so that the pins 401 protrude into operativeposition within the passageway. As described above, the embossedcharacter read head 350 is lowered into the passageway when the solenoid235 (not shown) is energized and the cam 355 rotates slightly to exertdownward pressure on the read head 350 to move the read head into itssecond position.

Once the embossed character read head 350 is positioned in the cardslot, the drive rollers 200 move the card 20 back toward the opening ofcard slot 60. FIG. 11G illustrates the interaction between pins 401 andthe embossed characters 35 as the card moves beneath the read head. Thebiasing ramp 390 ensures that the embossed characters are biasedupwardly against the pins during an embossed read cycle. The read head350 provides electrical signals corresponding to the embossedcharacters. These signals are decoded by control circuitry (not shown)as described in the referenced Embossed Character Reader Application.

After the embossed characters are detected by the read head 350, thecard read cycle, comprising any magnetic stripe reading subcycle(s) andany embossed character reading subcycle(s), is complete. At this point,the drive roller 200a ejects the card by driving it partially out of thecard slot 60, so that the operator may grasp and remove the card. As thecard is ejected, the embossed character read head 350 is retracted fromthe passageway 448 so that the reader 155 returns to the idle stateillustrated in FIG. 11A, and is again ready for another card to beinserted.

FIG. 12 shows the inside portion of the transport top portion 250. Theembossed character read head subassembly 350, cam mounting blocks 305,and lever 295 are shown in phantom for reference. When a credit card(not shown) is inserted in card slot 60, the embossed characters areguided by narrow parallel embossing guide ribs 450a, b in the passagewayalong a path adjacent the embossed character read head 350. The guideribs 450 extend slightly from the surface of the top portion 250 andinto the passageway. The guide ribs 450 also diverge slightly at theentrance of slot 60 in order to act as a "funnel" and direct theembossing into the slot 60. Inasmuch as the distance from the edge of acredit card to the characters embossed on the card may vary slightlyfrom one card type to another, the guide ribs 450 help compensate forthese variations and ensure that the embossing is always directed underthe embossed character read head 350.

The width W_(P) of the card passageway 448 is defined by the inner edges457 of the transport top portion 250. The exterior width W_(T) of thetop portion is defined by outer walls 458.

An elongate ejector groove 451 is provided in the top portion 250, atthe end opposite the insertion slot 60, for supporting and guiding anejector bar 470 (FIG. 14) for extricating a stock card. The ejector bar470 works substantially as described in the referenced Embossed CardReader Application, in that it includes a generally "L" shaped foot thatnormally lies at the barrier 361 of the slot and provides a means forejecting a card that becomes jammed in the reader when the ejector baris pulled outwardly along the groove 451.

In order to obtain an accurate magnetic stripe read, it is important toreduce or eliminate any feature of the transport top portion 250 thatprovides friction between the credit card and the top portion, orotherwise interferes with the travel of the credit card along thepassageway. Those skilled in the art will understand that any abruptchanges in the velocity of a credit card due to friction or other causesmay interfere with the magnetic read cycle. This is because the signalsread from the magnetic stripe will temporally vary in response tovelocity changes in the card as it encounters or leaves obstacles, ormeets with more or less friction as the card moves. Temporally varyingsignals are more difficult to reliably decode since they can bemisinterpreted.

In order to reduce friction, the transport top portion 250 employsintegrated outer card support ribs 455a, 455b, which, like the guideribs 450, extend slightly from the surface of the top portion 250. Thesecard support ribs 455 are very narrow, machined (or molded) with asmooth surface, and are positioned toward the outer edges of thepassageway so that only the outer edges of a card are in contact withthe ribs. The ribs 455 are defined in the top portion immediately insidethe inner edges 457.

When the card is moving within the card passageway, the outer cardsupport ribs 455 and guide ribs 450 are the only surfaces that engagethe top surface of the credit card. In this manner, the guide ribs 450and outer ribs 455 present a minimized surface area to touch a creditcard as it travels, and thus minimize the resistance (friction) tomovement of the card.

In order to further reduce the friction between the credit card and thetop portion 250, the top portion is preferably fabricated of injectionmolded plastic that has a low friction, low wear quality, such as acetylpolymer resins sold under the trademarks CELCON™ manufactured byCelanese Corp. or DELRIN™ manufactured by DuPont Co.

FIG. 13 shows the inside portion of the transport bottom portion 255.This view also illustrates the positioning of the drive rollers 200a, b,magnetic stripe read head 385, and biasing ramp 390. It will be seenthat the magnetic stripe read head 385 and the biasing ramp 390 arepositioned between the two drive rollers 200.

The interior width W_(B) of the bottom portion 255 is defined by theinner edges 460 that extend substantially the length of the bottomportion. The entire width W_(T) of the transport top portion 250 fits inthe width W_(B) between the inner edges 460 of the bottom portion whenthe transport top and bottom portions 250, 255 are mated together andattached to the bottom of the base plate 160.

A recess 462 is defined in the bottom portion 255 along a portion of theright side, so as to provide clearance for the ejector bar (not shown)as it moves to eject a card.

FIG. 14 is a front cross-sectional view of the interior of the cardpassageway 448, illustrating the relationship between a credit card 20,the magnetic stripe read head 385, and the embossed character read head350. Note that the slot 400 is preferably constructed such that the readhead 350 is supported in the manner described in referenced EmbossedCharacter Reader Application, with a lowered surface or recess forsupporting the wings 232 of the read head. The embossing guide ribs 450engage the embossed characters 35 and direct the card along a pathadjacent the embossed character read head 350. Along with outer ribs455, the guide ribs 450 engage the top surface of card 20 and provide asmooth, low friction interface between the transport top portion 250 andthe card 20.

The ejector bar 470 is shown looking down the passageway 448 with anupright portion behind the card 20 that fits in the ejector groove 451and engages with the card, a horizontal portion that slides along in therecess 462, and a downwardly extending portion that lies alongside thehousing.

Drive roller 200a, which appears in the foreground in FIG. 14, is shownin phantom for reference. The drive roller and magnetic stripe read head385 are held in place against the transport bottom portion 255 by rollerretainer cover 260. Drive sprocket 435 is shown exterior to thetransport bottom portion 255.

Control Circuitry

FIG. 15 is a block diagram of the electronic control circuitry 1000employed in the preferred multi-reader terminal 10. The circuitry isdesigned so that it implements an MS-DOS-compatible computer system.Those skilled in the art will appreciate that this facilitates theprogramming of the multi-reader terminal 10 by allowing programmers toutilize a wide variety of compilers, debuggers, and other developmenttools designed for the MS-DOS programming environment.

The circuitry 1000 includes a central processing unit ("CPU") 1005. Thepreferred CPU 1005 is a V-20 microprocessor manufactured by NECElectronics, Mountain View, Calif. The CPU is connected via a data bus1002 to a PC core logic circuit 1010, which provides signals that enablethe terminal 10 to operate as an MS-DOS-compatible computer system. Thepreferred core logic circuit 1010 is a type 82C100 manufactured by Chipsand Technologies, San Jose, Calif. Details of the preferredmicroprocessor and core logic circuit are available in the literaturesupplied by the manufacturers.

The circuit 1000 includes memory 1015 that provides both volatile andnon-volatile storage for the CPU 1005. The preferred memory includes256K bytes of dynamic RAM, 128K bytes of battery backed up static RAM,and an EPROM. The software stored in the EPROM includes a basicinput/output system (BIOS), an MS-DOS compatible disk operating system(ROM DOS), and a boot disk emulator (ROM DISK). The static RAM is usedto store terminal application software and terminal parameters in whatthose skilled in the art have denominated a "RAMDISK".

The CPU 1005 is connected to external serial port controllers 1020. Thepreferred terminal 10 includes two type 82C452 serial communicationscontrollers, manufactured by Startech Semiconductor, San Jose, Calif.Together, the external serial port controllers provide four individuallyprogrammable serial ports 62 that may used to communicate with a varietyexternal devices in many different configurations.

It will be recalled from the previous discussion of the exemplaryalternative configurations that the preferred terminal 10 includes aplurality of serial ports 62 that are used as communicating meanscomprising selectively configurable input and/or output terminals. Theseserial ports are used to receive data from various sources such as aconnected electronic cash register, signature capture pad, PIN pad, orother peripheral devices, and either respond to the data (as when thedata comprises a command to the terminal 10) or route the data toanother serial port so that it may be re-transmitted to the data'sproper destination.

While serial data ports are employed in the preferred embodiment ascommunication means, it should be understood that other types of datatransmitting/receiving communication means may be employed ascommunications means, such as optically coupled interface adapters(OCIA), keyboard wedge data devices, and other data communicationsdevices.

In order to provide versatile serial routing, the multi-reader terminal10 is programmed to constantly monitor each of the serial ports 62 forincoming data. When data is received, the multi-reader terminal 10responds appropriately, based upon the values of parameters that areavailable to customize the serial routing. These parameters arediscussed in greater detail in connection with the software for thepreferred embodiments. The flexibility provided by this parameter-drivenserial routing will allow end users many options on how to cable andconfigure their POS systems and utilize the present invention. In thepreferred terminal 10, serial parameters such as baud rate and flowcontrol may be individually set for each of the serial ports 62. Theseparameters are set by downloading data from a host computer system viaone of the serial ports.

The CPU 1005 is also connected via the bus 1002 to an internal serialport controller 1030, which is used to communicate with amicrocontroller 1035. The preferred internal serial port controller 1030is a type 16C450 manufactured by National Semiconductor Corp., SantaClara, Calif.

Microcontroller 1035 is used to interface with, and decode signalsreceived from, the card reader 155 and check reader 51. This data isthen transmitted to the CPU 1005, via internal serial port controller1030 and bus 1002. The preferred microcontroller 1035 is a type 80C31,manufactured by Signetics, Sunnyvale, Calif. The microcontroller 1035 isprovided with memory 1040, comprising 32K bytes of static RAM and 32Kbytes of ROM.

The microcontroller 1035 receives four different signals from the cardreader 155--(1) the optical encoder 330, (2) the magnetic stripe readhead 385, (3) the embossed character read head 350, and (4) the cardsensor 377. The optical encoder 330 provides signals indicative of theposition of the credit card within the card reader 155. The magneticstripe head 385 provides signals indicative of the data read from thecard's magnetic stripe. The embossed character read head 350 providessignals corresponding to the embossed characters on the card. The cardsensor 377 provides a signal indicating that a credit card has beeninserted into the card slot.

Once the card sensor signal has been received, the microcontroller 1035provides signals that control the motor 205 throughout a credit cardread cycle. The microcontroller 1035 also provides signals that controlthe solenoid 235, which determines whether the embossed character readhead 350 is retracted or is in position to contact the embossedcharacters 35 on credit card 20.

The microcontroller 1035 also receives signals from the MICR checkreader 51. Sensors 1050 associated with the preferred MICR readersubassembly 51 indicate the presence and approximate position of a checkthat is to be read. These signals are provided to the microcontroller1035. In response to these signals, the microcontroller sends signalsthat control the MICR motor 170 and cause the check to be carried pastthe MICR read head. Signals from the magnetic ink on a check are pickedup by a MICR read head 1055 associated with the preferred MICR reader51. These signals, which are indicative of the account data recorded onthe check, are provided to the microcontroller 1035, where the data isdecoded. This data is then provided to CPU 1005 via internal serial portcontroller 1030. Suitable circuitry for controlling the MICR motor andreceiving signals from the MICR read head may be obtained from Mag-Tek,Inc., Carson, Calif., the manufacturer of the preferred check reader 51.

Software for Control Circuitry

Turning now to FIG. 16, the preferred method 1100 of operating themulti-reader terminal 10 will be described. This method is implementedas software for the terminal's CPU 1005; this software is stored inmemory 1015, shown in FIG. 15. Generally, the method 1100 is operativeto receive commands in the form of serial data from a POS systemconnected to one of the serial ports 62, and to execute varioussubroutines responsive to those commands. Inasmuch as the multi-readerterminal 10 is designed to gather transaction data, the subroutines areprimarily directed to collecting data from the credit card reader 155 orMICR reader 51 that form a port of the multi-reader terminal, or fromperipheral devices such as a signature capture pad 95 or a PIN pad 110.

Before discussing the specific software modules, some background ishelpful to understand the overall operation of the terminal and thetypes of data parameters required to configure the terminal to providecertain features of operation. In order to allow maximum applicationflexibility, the preferred multi-reader terminal 10 maintains numerousparameters internally. These parameters enable the reconfiguration orexpansion of many of the advanced features of the multi-reader terminal.These parameters are structured in a file and record format, and storedin the battery backed static RAM 1015.

Generally, it will be understood that the preferred terminal isprogrammed to (1) respond to certain stimuli such as insertion of acredit card or check, and (2) respond to the receipt of commandsprovided to it from an external source, typically one of the serialports 62. The serial ports provide the general input and outputcommunication means for the terminal.

Various parameters of configuration are required to enable the terminalto provide certain features. A STORE PARAMETER command is used to modifythe current settings of these parameters without the need for a "full"or "partial" download. This command comprises sending the file andrecord number of the parameter to be modified, along with the new valueof the parameter. The multi-reader terminal 10 will then acknowledge thereceipt of the new value.

A RECALL PARAMETER command is used to retrieve the current value storedin any multi-reader terminal parameter. The operation of this command issimilar to the STORE PARAMETER command.

The parameter storage area in memory is preferably controlled withsecurity access. This access affects the STORE and RECALL functions.Individual records and/or entire files have one of three types ofsecurity available:

1) RW--Read/Write

2) RO--Read Only

3) N--No Access (cannot be stored or recalled)

Access to records of security types RO and N is permitted only with theuse an encrypted password. This feature, if supported by the POS system,will allow a transaction guarantor to update parameters on an "asneeded" basis. If the optional chargeback protection services are not ineffect, then security may be disabled.

External software associated with a connected POS terminal, or aconnected stand-alone personal computer used for configuration, notforming a part of the present invention, is employed to allow users toinspect and modify the values of the multi-reader terminal parameters.These functions may be supported by any computer complying with themulti-reader terminal communications standards.

The multi-reader terminal 10 is capable of receiving new downloads ofsoftware. A LOAD command will convey to the multi-reader terminal 10 thetotal number of files to be downloaded. When the multi-reader receivesthe command to enter LOAD mode, it will capture all incoming datareceived on an active serial port 62 until all of the downloaded fileshave been received.

When the LOAD command is received, the multi-reader terminal 10 storesall downloaded files in the appropriate directory in its internal memory(replacing older files with the same name and path). This downloadmethod allows "partial" downloads to take place simply by sending onlysome files. "Full" downloads can be accomplished by simply sending allof the files, but to be safe "full" downloads should be preceded by theERASE RAM command, which clean certain areas of memory dedicated toapplication programs.

The LOAD and ERASE RAM commands are only executed by the multi-readerterminal 10 when a second consecutive command is received, confirmingthe command.

When a multi-reader terminal 10 does not contain an application, theunit will automatically attempt to obtain a download. In this case, uponpower-up the multi-reader terminal 10 will transmit a REQUEST DOWNLOADcommand via its serial ports 62. If another multi-reader unit (with anapplication loaded) is connected via a direct serial link, a downloadwill occur.

Those skilled in the art will understand that a personal computer (PC)based utility program may be employed to effectuate downloads ofsoftware. Such a program should be made operative to provide "full" or"partial" downloads using files located on a local drive of the PC. Thisdownloading program may be given the additional capability ofcommunicating with other computers and receiving downloads from thesecomputers. It would then be possible to download files received fromother computers to multi-reader terminals 10. In any case, the abovesoftware downloading functionality can be ported to other computers(including POS systems) to allow for more convenient downloading ofsoftware into the multi-reader terminals units in the field. Thepreferred multireader is capable of receiving downloads over a directserial link from any computer complying with an appropriate downloadcommunications protocol, the details of which are within thecapabilities of the skilled artisan.

It will be recalled from the previous discussion of the exemplaryalternative configurations that the plurality of serial ports 62 areused as selectively configurable input and/or output terminals. Theseserial ports are used to receive data from various sources such aselectronic cash registers, signature capture pads, and other peripheraldevices, and either respond to the data (as when the data comprises acommand to the terminal 10) or route the data to another serial port sothat it may be re-transmitted to the data's proper destination. In orderto provide versatile serial routing, the multi-reader terminal 10 isprogrammed to constantly monitor each of the serial ports 62 forincoming data. When data is received, the multi-reader terminal 10responds appropriately, based upon the values of configurationparameters, described below, that are available to customize the serialrouting. Each serial port 62 is configured to one of the following fivestates:

1. Ignore all incoming data--all data received is discarded with noregard to the format and substance of the data.

2. Accept all incoming data as intended for

the multi-reader--data that conforms to valid multi-reader packetformats will be processed and acted upon accordingly. Data that does notfit into a recognized multi-reader format will be discarded.

3. Redirect all incoming data except for packets recognizable asintended for multi-reader--Data that conforms to valid multi-readerpacket formats will be processed and acted upon accordingly. Data thatdoes not fit into a recognized multi-reader format will be redirected tothe designated serial port.

4. Unconditional redirection--Data will be redirected to the designatedserial port with no regard to the format and substance of the data.

5. Multi-reader peripheral format--Data transmitted and received by thisserial port will not pass through the serial routing portion of themulti-reader. Ports of this type will be used by the multi-reader tointerface with external peripherals, such as the signature capture pad.

Turning now specifically to FIG. 16, the preferred method begins at step1105 where the terminal 10 is in an idle state, waiting to receive avalid command from a connected POS system or other device connected to aserial port 62. Once a command is received, the terminal 10 decodes thecommand and executes a corresponding appropriate subroutine in order toprovide the data requested by the POS system. Some of these subroutinesmight require prompting the merchant to perform certain actions, such as"INSERT CHECK IN READER", or "INSERT CREDIT CARD STRIPE DOWN", or "CARDREAD FAILURE--ENTER ACCOUNT NO. ON KEYPAD." Since the multi-readerterminal 10 does not have any input/output means such as an alphanumericdisplay or keypad, the terminal 10 is operative to provide signals tothe POS terminal to requesting that terminal to display an appropriatemessage on its display or request keypad input from the user. This wouldtypically be accomplished by means of a display 75 or keyboard 70located on an electronic cash register 65 (FIG. 1).

If the terminal 10 receives the an instruction to collect credit carddata, the method 1100 proceeds to step 1110, where it executes a "GETCREDIT CARD DATA" subroutine. Generally described, this subroutine isoperative to read the magnetic stripe and embossed characters of aninserted credit card in order to obtain the account number andexpiration date associated with the credit card account. Once the datais collected, the method 1100 returns to the idle state at step 1105.

If, at step 110 5, the terminal 10 receives an instruction to collectdata from a check, the method 1100 proceeds to step 1115 and executes a"GET CHECK MICR DATA" subroutine. At this point, the terminal 10attempts to collect the MICR data from the built-in MICR reader. Oncethe data is collected, the method returns to the idle state at step1105.

In some cases, the terminal 10 may be instructed to get the user'spersonal identification number (PIN) in conjunction with a debit cardtransaction. If a PIN pad 110 (FIG. 2) is attached to one of the serialports 62, the method 1100 proceeds to step 1120 and executes a "GET PIN"subroutine. After subroutine is completed, the method 1100 returns tostep 1105.

If a signature-capture pad 95 (FIG. 2) is attached, the terminal may berequested to collect the cardholder's signature in conjunction with acredit card transaction. The method then proceeds to step 1125 andexecutes a "GET SIGNATURE" subroutine. After the completion of thesubroutine, the method returns to step 1105.

In addition to the data collecting functions described above, theterminal 10 may also be instructed to perform various administrativeroutines 1130. These include functions such as resetting the terminal,providing status flap, providing error counts, and providing otherstatistical information. Inasmuch as those skilled in the art will befamiliar with these and other administrative functions, no furtherdescription will be provided herein.

The administrative routines 1130 also include serial port routingroutines and downloading routines. The serial port routing routines areoperative for responding to incoming communications on one of the serialports 62, determining the present configuration of the serial port onwhich the data was received, and forwarding the data or acting upon thedata, depending upon the serial port configuration. The variousconfigurations for the serial ports in the preferred embodiment isdescribed in greater detail below. The downloading routines areoperative in response to a LOAD command to receive a new program to beloaded in RAM 1015.

The routines 1110, 1115, 1120, and 1125 are preferably stored in the RAM1015, and are thus programs that are downloaded into the terminal via aserial port. Certain administrative routines 1130 are stored in RAM1015, while other administrative routines such as downloading routinesare preferably stored in the on-board ROM provided in the preferred CPU1005. Thus, the terminal is operative to "boot" from ROM on power-up andbe ready to load appropriate applications software upon receipt ofappropriate commands on the serial port. After booting from ROM, theterminal is ready to receive communications and commands via the serialports 62.

Turning now to FIG. 17, the preferred "GET CREDIT CARD DATA" subroutine1110 will be described. The routine begins at step 1150, where theterminal 10 sends a signal to the POS system requesting that a messagebe displayed instructing the operator to insert the credit card 20 intothe card slot 60. This message typically will be displayed on thedisplay 75 of a POS electronic cash register 65 (FIG. 2).

Once the display request is sent at step 1150, the microcontrollerenters a loop comprising steps 1155 and 1165. At step 1155, theterminals tests to see whether a credit card 20 has been inserted intocard slot 60. This test is conducted by looking for a signal from thecard sensor 377 (FIGS. 10, 15). If not, the method proceeds to step1165, where the terminal determines whether the POS system hastransmitted an "abort" command. If no abort command has been received,the method returns to step 1155 and re-enters the loop.

It should be understood that applications software running in aconnected POS host computer or in-store processor may provide for timingroutines awaiting insertion of a card, so that the terminal does notloop endlessly loop. If such timing routines are provided, uponexpiration the POS system may send an abort command, which will have theeffect of exiting the loop.

If the terminal determines that a card 20 has been inserted at step1155, the method branches to step 1170, and determines whether thecredit card transaction is to treated as a high risk transaction. Thisis determined by a flag set within terminal 10. One example of a highrisk situation is when the terminal is to be used in a store having ahistory of fraudulent transactions. In such a case, all transactions maybe treated as high risk, which enables special precautions fortransactions discussed below. The "high risk" flag may be set during aprogram download which loads software into the memory 1015.

If the transaction is not designated high risk, the method 1110 goes tostep 1175 and executes the "READ CARD DATA" subroutine. If thetransaction is high risk, the method goes to step 1180 and executes the"HIGH RISK CARD DATA" subroutine. Both subroutines control thecollection of the account data using the magnetic stripe reader and/orthe embossed character reader, and are described more completely below.Once the account data is read, the method 1110 proceeds to step 1185,where method 1110 returns to the method 1100.

Returning now to step 116 5 in FIG. 17, if the terminal determines thatan abort command has been received, the method proceeds to step 1185,where it returns to method 1100.

It should be noted that the preferred terminal 10 contains a card rangetable stored in its memory that enables it to determine which card typehas been read. If a card type validation parameter is enabled, thistable is used to determine if the card is of an acceptable type. Forexample, some merchants may accept VISA but not AMERICAN EXPRESS. Trackrestoration also uses the card range table (see discussion belowconcerning the "repair" of track data read from a magnetic stripe withdata read from the embossing). Restoration may be impaired or prohibitedif the card range table is not kept current.

Note further that each card type may be individually flagged as towhether or not chargeback protection is enabled by a transactionguarantor. The allowed methods of entry are determined by a chargebackprotection flag associated with each different card type in the cardrange table.

FIG. 18 is a flow diagram illustrating the preferred subroutine "READCARD DATA" 1175. Generally described, this subroutine is operative tocollect account data using the magnetic stripe reader and/or theembossed character reader, and to perform preliminary validity checks onthe acquired account number and expiration date.

The subroutine 1175 begins at step 1200, where the terminal attempts toread data from the magnetic stripe 30 on the credit card 20. The motor205 is actuated and the card is driven over the magnetic stripe readhead 385, generating magnetic stripe signals which are conditioned bycircuitry described in the referenced Data Card Terminal Application andprovided to the microcontroller 1035. The manner in which the card 20 isdriven over the magnetic stripe read head 385 is described above inconjunction with FIGS. 11A-11F. Once the card 20 passes over the readhead 385, the subroutine proceeds to step 1205.

The preferred magnetic stripe read head 385 is able to read both tracksI and 2 of the magnetic stripe 30. Accordingly, at 1205 the terminalfirst determines whether track 1 data is valid. The validity of thetrack data is determined by verifying the longitudinal redundancy check(LRC). If track 1 data is not valid, the subroutine 1175 proceeds tostep 1210 and determines whether track 2 data is valid. If not, thesubroutine proceeds to step 1215, and determines whether the terminalshould repeat its attempt to read data from the magnetic stripe. In thepreferred subroutine 1175, the terminal will attempt to read themagnetic stripe three times before proceeding to step 1220. If data fromeither track is determined to be valid at steps 1205 or 1210, thesubroutine proceeds to step 1250.

At step 1220, after attempts to read the magnetic stripe have failed,the terminal attempts to read the account number from the embossedcharacters 35 on the credit card 20. This is accomplished by energizingthe solenoid 235, and causing the embossed character read head 350 to belowered into the passageway 448 prior to driving the card 20 out of thecard slot 60 (see FIGS. 11A-11H). The card is then driven by the pins401 of the read head. Signals generated by the pins are provided to themicrocontroller 1035 and decoded as described in the referenced EmbossedCharacter Reader Application.

Once the embossed data is read, the subroutine 1175 proceeds to step1225 and determines whether the data read from the embossed characterreader (ECR) is valid. This is accomplished by performing a modulo 10check on the account number, as described in the referenced EmbossedCharacter Reader Application.

If, at step 1225, the data read from the embossed characters is found tobe valid, the subroutine 1175 advances to step 1230 and attempts torestore or "repair" the track 1 and/or track 2 data read from themagnetic stripe (which, it will be recalled, was not valid) bysubstituting the account number read from the embossed characters forthe account number read from the magnetic stripe. This is described morefully in the referenced Data Card Terminal Application.

At steps 1235 and 1240, the terminal determines whether the repairedtrack I or track 2 data, respectively, is valid. If the data is found tobe valid at step 1235 or step 1240, the subroutine 1175 proceeds to step1250. If the data is not valid at either of steps 1235 or 1240, thesubroutine advances to step 1245 and instructs the POS system togenerate a message on display 75 instructing the merchant to enter theexpiration date via keyboard 70. This is necessary since in thedisclosed embodiment, the embossed character reader 350 reads only thoseembossed characters 35 that are representative of the account number andis not operative to read the embossed expiration data. The expirationdate is normally obtained automatically from the magnetic stripe, but ifthe stripe cannot be validly read, the expiration date will not beavailable. Thus, manual entry of the expiration date is required. Oncethe expiration date is received by the terminal 10, the subroutineadvances to step 1250.

As described above, the subroutine arrives at step 1250 only when validaccount data has been obtained from the magnetic stripe, the embossedcharacter reader, or from a combination of both. At step 1250, theterminal attempts to validate the account data by performing a rood 10check on the account number, determining whether the expiration date haspassed, and determining whether the account number indicates that thecredit card is of a type supported by the terminal. If track data isreceived, it will be checked with industry standards. If card typevalidation is-enabled and the track data is valid, the card type will bechecked against the cards accepted with the card range table. Ifchargeback protection is enabled for this card, chargeback logic isapplied. If high risk is enabled, then the card information will beconfirmed using data acquired through multiple entry methods.

The valid track and associated data will be passed back to the POSsystem if all requirements have been satisfied. If any errors occur, acode indicating the particular error is returned to the POS system.Thus, once the tests are performed at 1250 and the results examined forvalidity at 1251, the subroutine either advances to step 1255 andprovides the appropriate data or branches to 1265. After the data isprovided, the subroutine advances to step 1260 and returns to method1110.

Returning to step 1225 in FIG. 18, the procedure for responding toinvalid embossed data will be described. If the account number read fromthe embossed characters is invalid because of a faulty LRC, thesubroutine 1175 goes to step 1265 and determines whether manual accountnumber entry is allowed. This is determined by a flag set within theterminal during program download. If manual entry is not allowed, thesubroutine goes to step 1270, where it provides an error message to thePOS system, indicating that the credit card reading failed. A failedreading generally will not be chargeback protected by a transactionguarantor. The merchant may proceed with the transaction at his ownrisk, or request an alternative form of payment. At step 1260, thesubroutine returns to method 1110.

If, at step 1265, the terminal determines that manual account numberentry is permitted, the subroutine goes to step 1275, where it instructsthe POS system to display a message on display 75 instructing themerchant to enter the account number and expiration date via keypad 70.Once the display instruction is sent to the POS system, the multi-reader10 is no longer needed in connection with the transaction and thesubroutine proceeds to step 1260, where it returns to method 1110.

FIG. 19 is a flow diagram illustrating the preferred "HIGH RISK CARDDATA" subroutine 1180. Like the subroutine "READ CARD DATA" 1175described above, the subroutine 1180 is operative to collect accountdata using the magnetic stripe reader and the embossed character reader,and to perform preliminary validity checks on the account number andexpiration date. However, the subroutine 1180 will return a messageindicating the card is unacceptable unless the account number read fromthe magnetic stripe 30 matches the account number read from the embossedcharacters 35. By requiring that the account numbers read from these twoseparate sources on the card match, an additional degree of assurance isprovided that the credit card is a valid, unaltered credit card.

Generally, "high risk" logic is only enabled if chargeback protection isenabled and a high risk parameter is active. This logic is onlyapplicable to sale transactions. For relevant transactions, thefollowing logic for entering the account number will be used:

1) When a card is inserted, the multi-reader 10 will read the track(s)that are present on the card (track 1 and/or track 2). The multi-readerwill determine which track is valid and use that track.

2) If the track data was not successfully read, the multi-reader willreturn status information that the card is unacceptable and another formof payment must be used.

3) The multi-reader will read the embossing from the card. After themaximum number of unsuccessful attempts have been made at reading theembossing, the multi-reader will return status that the card isunacceptable and another form of payment must be used.

4) Once the magnetic stripe data and embossed data have beensuccessfully read, the multi-reader will compare the account numbers inthe mag stripe data and the embossed data. If they are different, themulti-reader will return status that the card is unacceptable andanother form of payment must be used.

After the foregoing steps, the multi-reader will proceed with thetransaction (check the expiration date, perform a MOD 10 check, etc.)and then return the collected data to the POS system.

In FIG. 19, the HIGH RISK CARD DATA subroutine 1180 begins at step 1300,where the terminal attempts to read data from the magnetic stripe 30 onthe credit card 20. The manner in which the card 20 is driven over themagnetic stripe read head 385 is described above in conjunction withFIGS. 11A-11F. Once the Card 20 passes over the read head 385, thesubroutine proceeds to step 1305. Since the preferred read head 385 isable to read both tracks 1 and 2 of the magnetic stripe 30, the terminalfirst determines whether track 1 data is valid. The validity of thetrack data is determined by verifying the longitudinal redundancy check(LRC). If track 1 data is not valid, the subroutine 1180 proceeds tostep 1310 and determines whether track 2 data is valid. If not, thesubroutine proceeds to step 1315, and returns a message to the POSsystem indicating that the card 20 is unacceptable and another form ofpayment should be used. From step 1315, the subroutine goes to step1320, where it returns to the method 1110.

Returning now to steps 1305 and 1310, if either track 1 or track 2 datais found to be valid, the subroutine 1180 advances to step 1325, wherethe terminal attempts to read the embossed characters 35. At step 1330,the subroutine determines whether the embossed data is valid by checkingthe modulo 10 of the read account number. These validations, theprogramming for which is within the skill of the art, are effected inaccordance with ANSI Standard X4.13-1983, which include various checkssuch as the Luhn formula, longitudinal redundancy checks (LRC), modulo10 checks, etc., as set forth in the ANSI standard. If the data is notvalid, the subroutine proceeds to step 1315, and continues as describedabove. If the embossed data is valid, the subroutine goes to step 1335.

At step 1335, the subroutine determines whether the account number readfrom the embossed characters 35 is identical to the account number readfrom the magnetic stripe 30. If not, the subroutine proceeds to step1315, and continues as described above. If so, the subroutine proceedsto step 1340, and attempts to validate the account data by performing arood 10 check on the account number, prompting for manual entry of theexpiration date, determining whether the expiration date has passed, anddetermining whether the account number indicates that the credit card isof a type supported by the terminal.

Once the data validation tests of step 1340 are performed, thesubroutine advances to step 1342, where the inquiry is made whether thedata is valid in accordance with the tests performed. If not, theroutine branches to 1315 where the "CARD UNACCEPTABLE" message is sent.If the data is valid, the routine branches to step 1345 and provides theappropriate data message to the POS system. After the data is provided,the subroutine advances to step 1320 and returns to method 1110.

FIG. 20 is a flow diagram illustrating the preferred "GET CHECK MICRDATA" subroutine 1115. The subroutine begins at step 1400 by sendingdata to the POS system requesting that a message be displayedinstructing the operator to insert a check 15 into MICR slot 50. Afterthe instruction is transmitted to the POS system, the subroutineproceeds to step 1405 and determines whether the check has beeninserted. Insertion of a check is detected by circuitry associated withthe preferred MICR reader 51 that provides a signal to themicrocontroller 1035 (FIG. 15). If not, the subroutine goes to step 1410and determines whether the terminal has received an abort command.

If the terminal has received an abort message, the subroutine goes tostep 1420 and returns to method 1100. If the terminal has not receivedan abort message, the subroutine loops back to step 1405 and retests forcheck insertion and abort. Again, it will be understood that the POSsystem may provide for timing routines and provision of an abort commandupon expiration so that the microcontroller does not endlessly loopawaiting check insertion.

If, at step 1405, the terminal determines that a check has been insertedinto MICR slot 50, the subroutine proceeds to step 1425 and reads thedata from the magnetic ink characters 25 printed along the bottom edgeof the check 20. At step 1430 the terminals determines whether thenumerical data from the check is valid by calculating a checksum on thedigits of the number and comparing the checksum to a verifier digitprovided in the number, in the manner as will be known to those skilledin the art. If the check data is valid, the subroutine proceeds to step1435 and transmits the check account number data to the POS system. Thenthe subroutine advances to step 1420 and returns to method 1100. At thePOS system, the transaction data entered by the merchant is associatedwith the account number from the check. This data may also beelectronically submitted for payment or for transaction guarantee ifappropriate arrangements have been made with a check transactionprocessor or guarantor.

If the check data is found to be invalid at step 1430, the subroutineadvances to step 1440, and sends a message to the POS system indicatingthe read failed. In the case of failure of the MICR reading, and if themerchant still wants to accept a check, the check data will need to beentered via the keyboard 70 on the electronic cash register 65. Amessage is thus sent to the POS terminal that the MICR reading failed,and requesting a prompt to enter the check account number manually oraccept an alternative form of payment. After the message is sent to thePOS terminal, the subroutine proceeds to step 1420, where it returns tomethod 1100.

FIG. 21 is a flow diagram illustrating the preferred "GET PIN"subroutine 1120. It is assumed that a PIN pad 110 (FIG. 2) is connectedto one of the serial ports 62, and that this serial port has beenidentified to the software. The subroutine begins at step 1500 byresetting the PIN pad 110 with appropriate reset signals. At step 1505,the terminal causes the PIN pad 110 to display a message on display 120instructing the cardholder to enter his or her PIN. Once the message hasbeen displayed, the subroutine proceeds to step 1510.

At step 1510 the terminal determines whether the PIN data has beenentered via keypad 115. If not, the subroutine goes to step 1515 andtests whether the terminal has received an abort command. If the abortcommand has not been received, the subroutine loops back to step 1510.If the abort has been received, the subroutine goes to step 1525 andreturns to method 1100.

Returning to step 1510, if PIN data has been entered, the subroutinegoes to step 1530 and stores the PIN data. From step 1530, thesubroutine proceeds to step 1535, where the PIN data is provided to thePOS system. Inasmuch as many data card magnetic stripes carry an encodedPIN number, the entered PIN data may be compared to a PIN acquired fromthe magnetic stripe in the terminal 10 to validate the transaction.After the PIN data is provided to the POS system, the subroutine goes tostep 1525, and returns to method 1100.

FIG. 22 is a flow diagram illustrating the preferred "GET SIGNATURE"subroutine 1125. It is assumed that a signature capture pad 95 (FIG. 2)with digitizer and special pen is connected to one of the serial ports62, and that this serial port has been identified to the software. Thepreferred signature capture pad, and the operation thereof, is describedin the referenced Data Card Terminal Application.

Generally, a connected POS system will send a command to themulti-reader 10 to capture a signature. The POS system will then remainin a loop checking for response from the multi-reader. The POS systemwill be asked to display a message and/or give a user response from thekeyboard to the multi-reader while in this loop. The loop is exited whena successful response is received, a failure response is received, or anabort process is initiated by the user.

When the multi-reader receives a GET SIGNATURE command, it will resetthe signature pad and prompt the user (through the POS system) to placethe receipt on the pad and have the customer sign it. The multi-readerwill wait for signature data from the pad until data is received, or atimeout occurs. Generally, the timing routines are carried out in thePOS system, and an abort command is sent to the terminal if the timersexpire.

If valid data is received, it is sent back to the POS system with asuccess code. If invalid data is received, the multi-reader requests thesignature pad to resend the data. If a timeout occurs or the signatureis too big, the merchant will be polled as to whether or not thecustomer has attempted to sign. If the customer has not started asignature, the process will be repeated until the customer attempts asignature or an abort key on the POS terminal is pressed. If thecustomer has attempted to sign, the user will be prompted to have thecustomer sign again.

If the timer expires on the second attempt and the merchant answers thatthe customer has signed, the transaction will be processed without thesignature. This constitutes a critical error condition with thesignature pad. The multi-reader will return a critical error status andthe POS system should alert the user until the condition is corrected.

If the signature was captured a second time but it is still too big, itwill be truncated at the maximum allowable size.

Referring now specifically to FIG. 22, the GET SIGNATURE subroutine 1125begins at step 1600 where the terminal 10 sends a reset signal to thesignature capture pad 95, which causes the signature capture pad toreset itself and prepare to receive a signature. At step 1605, theterminal instructs the POS system to display a message or promptdirecting the merchant to place a paper receipt on the signature capturepad 95 and have the cardholder sign the receipt on the pad. This messageis displayed on the display 75 of the electronic cash register 65. Thesubroutine the proceeds to step 1610 and waits to receive signature dataor an abort command.

At step 1610, the subroutine determines whether the customer hasattempted a signature or whether an abort command has been received. Ifa signature has been attempted, signature signals will be provided fromthe signature pad as described in the referenced Data Card TerminalApplication. Again, the POS system will preferably maintain a timer toawait receipt of the signature signals, and send and abort command if nosignature signals are received by the POS before the timer expires. Ifthe abort command is received, the routine branches to 1645 and returnsto the idle state.

If the customer has attempted a signature, the program branches fromstep 1610 to step 1630, where the inquiry is made whether data has beenreceived from the signature pad. If not, the routine branches to step1640, and provides an appropriate error message. If data has beenreceived from the signature pad, the routine branches to step 1675,where the inquiry is made whether the data is valid. If not valid, theroutine branches to step 1640. If the data is valid, the routinebranches to step 1655.

At step 1655, the signature signals are compressed and provided as anoutput of compressed signature signals, in accordance with thedescription in the referenced Data Card Terminal Application. In the POSsystem, the signature data is associated with other transaction data andforwarded to a transaction processor or guarantor for payment orchargeback protection, as described in the referenced Data Card TerminalApplication. The routine then returns to the idle state at step 1645upon the completion of data transmission to the POS system.

It should be understood that various alterations of the operation of thesignature pad are contemplated. The terminal may direct the POS systemto display a message inquiring whether the cardholder has attempted tosign the receipt. If the response is no, the POS system may againdisplay a message instructing the cardholder to sign the receipt.

Multi-Reader Communication Protocol

Next will be discussed the preferred command/response formats orcommunications protocols utilized in the present invention to providecommands to the terminal 10 via one of the serial ports 62.

First consider packets from a connected POS system to the multireader.There are two basic types of commands in the multi-reader command set.The first type is a simple isolated command that requires no furtherinteraction such as RESET MULTIREADER and GET STATUS FLAGS. The othertype of command places the multi-reader into one of several interactivemodes and begin a session where the will drive the process.

Examples of commands that place the multi-reader into an interactivemode include GET CREDIT CARD DATA and GET SIGNATURE. After receiving amode command, the multi-reader will command action through predefinedresponse messages. Ultimate control, however, will reside with theparent device such as a PC or an intelligent electronic cash register.

Multi-reader commands are always preceded by an attention byte and endedwith a terminator byte. These values are stored as parameters and may bechanged using the STORE PARAMETER command. A command byte in the packetcontains the command indicating the operation to be performed by themulti-reader. If the POS system is merely replying to a multi-readerrequest for data, the command will be a space (Hex 20). If the POSsystem is sending data to the multi-reader, the data will follow thecommand byte.

The preferred format for a command block is as follows, where F=flag(`0`,`1`), 9=a numeric field varying from (`0`. . . `9`), and X=analphanumeric field. Field sizes are shown in parentheses:

    ______________________________________                                        COMMAND BLOCK:                                                                ______________________________________                                        Multi-Reader Attention                                                                             X(1) [DCl]                                               Multi-Reader Confirmation                                                                          X(1) [`M`]                                               Command              X(1)                                                     Data from the POS system                                                                           X(nnn) [optional]                                        Terminator           X(1) [CR]                                                ______________________________________                                    

Packets from the multi-reader 10 to a POS system, which are typicallyresponses from the terminal 10, are always preceded by an attention byteand ended with a terminator byte. These values are also stored asparameters and may be changed using the STORE PARAMETER command. Themode byte is the current operation mode of the multi-reader. The returncode indicates the purpose of this packet. The message number is azero-filled indicator for which message (if any) should be displayed bythe POS system. If the multi-reader is sending data to the POS system,the data follows the message bytes.

    ______________________________________                                        RESPONSE BLOCK                                                                ______________________________________                                        Host Attention       X(1) [DC1]                                               Host Confirmation    X(1) [`H`]                                               Mode                 9(1)                                                     Return code          9(1)                                                     Message number       9(2)                                                     Data from the Multi-Reader                                                                         X(nnn) [optional]                                        Terminator           X(1) [CR]                                                ______________________________________                                    

Valid modes for the preferred multi-reader are:

    ______________________________________                                        0            IDLE state                                                       1            GET CREDIT CARD DATA                                             2            GET CHECK MICR DATA                                              3            GET PIN                                                          4            GET SIGNATURE                                                    5            LOAD                                                             6            DIAGNOSTICS                                                      ______________________________________                                    

Valid return-codes for the preferred multi-reader are:

    ______________________________________                                        0       No special action required                                            1       Get input from the POS system                                         2       Critical error has occurred                                           3       Data sent from multi-reader to the POS system                         ______________________________________                                    

Valid message number ranges for the preferred multi-reader are:

    ______________________________________                                        00              No message to display                                         01-49           General messages                                              50-89           Error messages                                                90-99           Critical error messages                                       ______________________________________                                    

Data designated above as "optional" is made up of zero or more dataelements. This data is only present if the return code has a value of 3.The format of this data varies depending upon the command sent by thePOS system to initiate the data exchange. The individual commanddescriptions provide detailed information on the specific data that canbe returned when that command is sent to the multi-reader.

The preferred command set for a multi-reader terminal 10 constructed inaccordance with the present invention is as follows, where "M" is a modeas described above, "R" is a response or return code as described above,"Msg" is a message number as described above, and "Opt" is the optionaldata described above:

    ______________________________________                                        ABORT PREVIOUS COMMAND                                                        Command:    `A` (Hex 41)                                                      Function:   Aborts current mode and returns multi-                                        reader to idle state.                                             Returns:    M R Msg Opt                                                                   0  0 00   // Idle reached                                         RESET MULTIREADER                                                             Command:    `R` (Hex 52)                                                      Function:   Reset the multi-reader to power-up state.                                     (Reboots multi-reader).                                           Returns:    M R Msg Opt                                                                   0  0 00                                                           ERASE RAM                                                                     Command:    `E` (Hex 45)                                                      Function:   Delete any existing programs and data                                         from the multi-reader. The return value                                       will be sent immediately before the erase                                     occurs. After erasing the disk, the multi-                                    reader will reboot and enter a wait loop                                      where it is waiting for a LOAD                                                command. This command must be                                                 confirmed before it will be executed.                             Returns:    M R Msg Opt                                                                   0  0 00                                                           GET ID                                                                        Command:    `I` (Hex 49)                                                      Function:   Requests the identification of the multi-                                     reader.                                                           Returns:    M R Msg Opt                                                                   0  3 00  00 ID                                                    GET STATUS FLAGS                                                              Command:    `F` (Hex 53)                                                      Function:   Requests the current status of the multi-                                     reader. Can be done at any time.                                  Returns:    M R Msg Opt                                                                   ?  3 00  01  Swipe Error, Emboss                                              Error, MICR Error, Signature Error,                                           Memory Error                                                      X(1)X(1)X(1)X(1)                                                              GET STAT COUNTS                                                               Command:    `Q` (Hex 46)                                                      Function:   Requests the current status of the multi-                                     reader status counts.                                             Returns:    M R Msg Opt                                                                   0  3 00  02  Stat Designator, Count                                           Value, . . .                                                      X(2)X(2) . . .                                                                CLEAR STAT COUNTS                                                             Command:    `K` (Hex 4B)                                                      Function:   Clears the current multi-reader status                                        counts.                                                           Returns:    M R Msg Opt                                                                   0  0 00                                                           STORE PARAMETER                                                               Command:    `Y` (Hex 59)                                                      Data:       <FILE><FIELD><PASSWORD><DATA>                                                 9(2)9(2)X(8)X(Variable)                                           Function:   Multi-reader will store the data value                                        contained in the command packet in the                                        indicated location.                                               Returns:    M R Msg Opt                                                                   0  0 00                                                                       0  0 70   // File does not exist                                              0  0 71   // Field does not exist                                             0  0 72   // Access denied                                                    0  0 73   // Error opening file                                   RECALL PARAMETER                                                              Command:    `X` (Hex 58)                                                      Data:       <FILE><FIELD><PASSWORD>                                           9(2)9(2)X(8)                                                                  Function:   multi-reader will return the data value                                       contained in the indicated location.                              Returns:    M R Msg Opt                                                                   0  3 00  03 Data From File:Field                                              0  0 70   // File does not exist                                              0  0 71   // Field does not exist                                             0  0 72   // Access denied                                                    0  0 73   // Error opening file                                   GET CREDIT CARD DATA                                                          Command:    `C` (Hex 43)                                                      Data:       <TRAN.sub.-- TYPE>                                                            Valid transaction types include:                                             1 = Sale transaction                                                          2 = MOTO transaction                                                          0 = Any other transaction (Default)                                Function:   Puts the multi-reader into Get Credit                                         Card Data mode. The multi-reader may                                          transfer control to the POS system in                                         order to obtain keyboard input.                                   Returns:    M R Msg Opt                                                                   * Return values *                                                             0  3 00  10 Entry Mode, Guarantee,                                                Account No., Exp. Date                                        X(1)X(1)X(19)MMYY                                                                         0  3 00  11 Entry Mode, Guarantee,                                                Track 1                                                       X(1)X(1)X(80)                                                                             0  3 00  12 Entry Mode, Guarantee,                                                Track 2                                                       X(1)X(1)X(40)                                                                 * Display message and return to IDLE *                                                  0  0 50                                                                              // Card type not accepted                                              0  0 51                                                                             // Card unreadable                                                      0  0 52                                                                             // Card is expired                                                      0  0 53                                                                             // Card is not yet valid                                                0  0 54                                                                             // Invalid Account Number                                               0  0 55                                                                             // Card unacceptable                                                          (High Risk violation)                                         * Display message and continue *                                                        1  0 10                                                                             // Insert card into card                                                      reader                                                                  1  0 11                                                                             // Remove card                                                * Display message and accept data *                                                     1  1 12                                                                             // Get expiration date                                                  1  1 13                                                                             // Get issue date                                                       1  1 14                                                                             // Get account number                                         * Critical errors *                                                                     1  2 90                                                                             // Swipe reader malfunction                                             1  2 91                                                                             // Emboss reader                                                              malfunction                                                   GET CHECK MICR DATA                                                           Command:    `M` (Hex 4D)                                                      Function:   Puts the multi-reader into the Get Check                                      MICR Data mode. The multi-reader will                                         stay in this mode until the MICR number                                       has been read or an ABORT command is                                          send from the POS system.                                         Returns:    M R Msg Opt                                                                 0  3 00                                                                             20 MICR Number data                                                     2  0 20                                                                              // Prompt user to insert                                                      check                                                                  2  0 21                                                                              // Reinsert check                                                      2  0 22                                                                              // Remove check                                                        0  0 23                                                                              // Bad read                                                            0  2 92                                                                              // MICR reader                                                                malfunction                                                  GET PIN                                                                       Command:    `P` (Hex 50)                                                      Function:   Places the multi-reader into PIN Entry                                        mode. The customer will be allowed to                                         enter a PIN on the PIN pad.                                       Returns:    M R Msg Opt                                                                 0  3 00 PIN data accepted by                                                          PIN reader                                                            3  0 30                                                                              // Prompt user to enter PIN                                            0  2 93                                                                              // PIN pad not responding                                    GET SIGNATURE                                                                 Command:    `S` (Hex 53)                                                      Function:   Instructs the multi-reader to get a                                           signature. Signature will be returned in                                      a transmittable form.                                             Returns:    M R Msg Opt                                                                   0  3 00  40 Length, Signature,                                                Checksum                                                          9(4)X(1-2000)X(1)                                                                       4  0 40                                                                             // Have the customer sign.                                              4  1 41                                                                             // Did the customer sign?                                               4  0 42                                                                             // Signature pad not                                                          responding                                                              0  0 43                                                                             // Signature pad not                                                          attached                                                                0  2 94                                                                             Signature pad malfunction                                     LOAD                                                                          Command:    `L` (Hex 4C)                                                      Function:   Places the multi-reader in LOAD mode.                                         This command is used to load program                                          data to the multi-reader. While in the                                        LOAD mode, the multi-reader will use a                                        communications protocol designed for                                          high-speed error free transmission of                                         large data files. Because the protocol                                        will be different for this process, the                                       multi-reader will not respond to normal                                       commands that are received during the                                         LOAD process. This command must be                                            confirmed before it will be executed.                             Returns:    M R Msg Opt                                                                 5  0 00                                                                               // Entering Load mode                                       REQUEST DOWNLOAD                                                              Command:    `+`                                                               Function:   Indicates a desire to receive a download                                      from the device connected to the serial                                       port.                                                             Returns:    None                                                              DIAGNOSTICS                                                                   Command:    `D` (Hex 44)                                                      Data:       <MODE>                                                            Function:   Puts the multi-reader into diagnostics                                        mode. The mode sent after the `D` is the                                      mode to test                                                      Returns:    M R Msg Opt                                                                   0  0 00                                                           (Many of the return packets described above                                   can be encountered when using various areas                                   of diagnostics.)                                                              RETRANSMIT LAST PACKET                                                        Command:    `=` (Hex 3D)                                                      Function:   Command used to request that the multi-                                       reader resend the last packet transmitted                                     to the POS system.                                                Returns:    N/A                                                               DATA COMMAND                                                                  Command:    ` ` (Hex 20)                                                      Data:       <various data>                                                    Function:   Command used to transmit data to the                                          multi-reader after the multi-reader has                                       requested user input.                                             Returns:    M R Msg Opt                                                                   0  0 00                                                           ______________________________________                                    

It will be recalled from the discussion above that various messagescodes ("Msg") are transmitted by the multi-reader terminal 10 undercertain conditions, to convey various information. Exemplarymulti-reader messages in the preferred embodiment include the following:

General Messages:

10-Insert card into card reader

11-Remove card

12-Get expiration date

13-Get issue date

14-Get account number

20-Insert check into MICR reader

21-Reinsert check

22-Remove check

23-Bad read

30-Have the customer enter their PIN (GET PIN)

40-Have the customer sign (GET SIGNATURE)

41-Did the customer sign?

42-Signature pad not responding

43-Signature pad not attached

Error Messages

50-Card not allowed

51-Card unreadable

52-Card is expired

53-Card is not yet valid

54-Invalid account number

55-Card unacceptable

70-File does not exist

71-Field does not exist

72-Access denied

73-Error opening file

74-Invalid diagnostics command

Critical Error Messages:

90-Magnetic Stripe Ruder Malfunctioning

91-Emboss Reader Malfunctioning

92-MICR Ruder Malfunctioning

93-PIN Pad Not Responding

94-Signature Pad Malfunctioning

Multi-Reader Parameters

The preferred terminal 10 is configurable in a number of respects.Various status and configuration information is stored in memory, andreferred to by various software routines so that appropriate action istaken, appropriate responses are provided. Various status indicators orflags are utilized to store configuration or status information. Certainof these flags are accessible by an application program running on aconnected POS system, while others are not. In the following discussion,security for various flags is indicated by N=NOT ACCESSIBLE, RO=READONLY, RW=READ/WRITE. Formats are denoted as F=flag (`0`,`1`), 9=anumeric field varying from (`0`. . . `9`), and X=an alphanumeric field.Field sizes are shown in parentheses.

The status flags are stored in files in memory. The identity of variousstatus and parameter files in the preferred embodiment are as follows.The Active Options file is used to store the status of variousperipherals and other devices utilized in the present invention. Notethat the High Risk flag referred to in FIG. 17 is stored here:

    ______________________________________                                        Active Options -- File 00                                                     ______________________________________                                        00 Embossed Data Reader Active                                                                   RW F(1) 0=NO, 1=YES                                        01 Magnetic Stripe Reader Active                                                                 RO F(1) 0=NO, 1=YES                                        02 PIN Pad Active  RW F(1) 0=NO, 1=YES                                        03 Signature Pad Active                                                                          RW F(1) 0=NO, 1=YES                                        04 MICR Reader Active                                                                            RO F(1) 0=NO, 1=YES                                        05 High Risk Active                                                                              RO F(1) 0=NO, 1=YES                                        06 MOTO Capability Active                                                                        RW F(1) 0=NO, 1=YES                                        07 Manual Entry Allowed                                                                          RO F(1) 0=NO, 1=YES                                        08 Entry Devices Active at Idle                                                                  RW F(1) 0=NO, 1=YES                                        09 Card Type Validation Active                                                                   RW F(1) 0=NO, 1=YES                                        ______________________________________                                    

A data file denominated Card Acceptance is employed to store informationconcerning particular types of credit card supported by the terminal. Anexemplary file in the preferred embodiment is as follows:

    ______________________________________                                        Card Acceptance -- File 01                                                    ______________________________________                                        00 VISA Acceptance Flag                                                                           RW F(1) 0=NO, 1=YES                                       01 MasterCard Acceptance Flag                                                                     RW F(1) 0=NO, 1=YES                                       02 (other) Acceptance Flag                                                                        RW F(1) 0=NO, 1=YES                                       03 Discover Acceptance Flag                                                                       RW F(1) 0=NO, 1=YES                                       04 American Express Acceptance                                                                    RW F(1) 0=NO, 1=YES                                         Flag                                                                        05 Carte Blanche Acceptance Flag                                                                  RW F(1) 0=NO, 1=YES                                       06 Diner's Club Acceptance Flag                                                                   RW F(1) 0=NO, 1=YES                                       07 (other) Acceptance Flag                                                                        RW F(1) 0=NO, 1=YES                                       08 ABA Standard Prop. Acc. Flag                                                                   RW F(1) 0=NO, 1=YES                                       09 Non ABA Standard Prop. Acc.                                                                    RW F(1) 0=NO, 1=YES                                         Flag                                                                        ______________________________________                                    

As described in the referenced Data Card Terminal Application, certaintypes of transactions will be chargeback protected by a transactionguarantor, assuming that data concerning the form of payment is obtainedby the terminal and properly associated with the transaction dataacquired by a connected electronic cash register. For example, certaintransactions involving particular credit cards can be chargebackprotected. In the preferred embodiment, a data file is stored in memoryto indicate which (if any) particular types of credit cards arechargeback protected to a merchant utilizing the system:

    ______________________________________                                        Chargeback Protection -- File 02                                              ______________________________________                                        00 VISA Chargeback Flag                                                                           RO F(1) 0=OFF, 1=ON                                       01 MasterCard Chargeback Flag                                                                     RO F(1) 0=OFF, 1=ON                                       02 (other) Chargeback Flag                                                                        RO F(1) 0=OFF, 1=ON                                       03 Discover Chargeback Flag                                                                       RO F(1) 0=OFF, 1=ON                                       04 American Express Chargeback                                                                    RO F(1) 0=OFF, 1=ON                                         Flag                                                                        05 Carte Blanche Chargeback Flag                                                                  RO F(1) 0=OFF, 1=ON                                       06 Diner's Club Chargeback Flag                                                                   RO F(1) 0=OFF, 1=ON                                       07 (other) Chargeback Flag                                                                        RO F(1) 0=OFF, 1=ON                                       08 ABA Standard Prop. CB Flag                                                                     RO F(1) 0=OFF, 1=ON                                       09 Non ABA Standard Prop. CB                                                                      RO F(1) 0=OFF, 1=ON                                         Flag                                                                        ______________________________________                                    

A data file is employed in the preferred embodiment for storage of namesassociated with various credit cards:

    ______________________________________                                        Card Names -- File 03                                                         ______________________________________                                        00 VISA Card Name        RW     X(12)                                         01 MasterCard Card Name  RW     X(12)                                         02 (other) Card Name     RW     X(12)                                         03 Discover Card Name    RW     X(12)                                         04 American Express Card Name                                                                          RW     X(12)                                         05 Carte Blanche Card Name                                                                             RW     X(12)                                         06 Diner's Club Card Name                                                                              RW     X(12)                                         07 (other) Card Name     RW     X(12)                                         08 ABA Standard Prop. Card Name                                                                        RW     X(12)                                         09 Non ABA Standard Prop. Card Name                                                                    RW     X(12)                                         ______________________________________                                    

A file is preferably employed for storage of range informationpertaining to certain types of credit cards, for example, ranges of thenumber of digits in a string comprising the account number and a rangeof valid (or expired) numbers. These ranges are employed to determinethe validity of the credit card account numbers detected utilizing themagnetic stripe reader and embossed character reader:

    ______________________________________                                        Card Ranges -- File 04                                                        ______________________________________                                        00 VISA Range 1 Info  N     X(Variable)                                       01 VISA Range 2 Info  N     X(Variable)                                       02 MasterCard Range Info                                                                            N     X(Variable)                                       03 (other) Range 1 Info                                                                             N     X(Variable)                                       04 (other) Range 2 Info                                                                             N     X(Variable)                                       05 (other) Range 3 Info                                                                             N     X(Variable)                                       06 (other) Range 4 Info                                                                             N     X(Variable)                                       07 (other) Range 5 Info                                                                             N     X(Variable)                                       08 (other) Range 6 Info                                                                             N     X(Variable)                                       09 Discover Range Info                                                                              N     X(Variable)                                       10 American Express Range 1 Info                                                                    N     X(Variable)                                       11 American Express Range 2 Info                                                                    N     X(Variable)                                       12 Carte Blanche Range Info                                                                         N     X(Variable)                                       13 Diner's Club Range 1 Info                                                                        N     X(Variable)                                       14 Diner's Club Range 2 Info                                                                        N     X(Variable)                                       15 Diner's Club Range 3 Info                                                                        N     X(Variable)                                       16 (other) Range 1 Info                                                                             N     X(Variable)                                       17 (other) Range 2 Info                                                                             N     X(Variable)                                       18 ABA Standard Prop. Range info                                                                    N     X(Variable)                                       19 Non ABA Standard Prop. Range                                                                     N     X(Variable)                                         Info                                                                        Card Range Info Format:                                                       Card Type              9(1)                                                   Separator              `/`                                                    Beginning Range        9(Variable)                                            Separator              `/`                                                    Ending Range           9(Variable)                                            Separator              `/`                                                    Card Number Length     9(2)                                                   ______________________________________                                    

A signature pad or PIN pad may be utilized in connection with thepresent invention. A connected signature pad or PIN pad is controlled inaccordance with various configuration parameters. Some of theseparameters involve the format for the signature signals provided fromthe signature pad, as described in the referenced Data Card TerminalApplication. Preferred parameters include the following:

    ______________________________________                                        Signature Capture/PIN Pad Values -- File 05                                   ______________________________________                                        00 Signature Pad Port Number                                                                           RW     9(1)                                          01 "Wait For Signature" Timeout                                                                        RW     9(3)                                          02 "Lift Pen" Timeout    RW     9(2)                                          03 "Signature Completion" Timeout                                                                      RW     9(2)                                          04 Max Bytes For Signature                                                                             RW     9(4)                                          05 Signature Resolution  RW     9(3)                                          06 Eight to Seven Bit Flag                                                                             RW     9(1)                                          07 PIN Pad Port Number   RW     9(1)                                          08 "Wait for PIN" Timeout                                                                              RW     9(3)                                          ______________________________________                                    

Information for configuring the serial ports 62 is also stored in a datafile, as follows:

    ______________________________________                                        Serial Port Configurations -- File 06                                         ______________________________________                                        00 Master Control Port Number                                                                    RW     9(1)                                                01 Multi-Reader Attention Byte                                                                   RW     X(1)                                                02 Multi-Reader Terminator Byte                                                                  RW     X(1)                                                03 Host Attention Byte                                                                           RW     X(1)                                                04 Host Terminator Byte                                                                          RW     X(1)                                                05 Serial Port 1 Baud Rate                                                                       RW     9(5)                                                06 Serial Port 1 Data Bits                                                                       RW     9(1)                                                07 Serial Port 1 Parity                                                                          RW     X(1)                                                08 Serial Port 1 Stop Bits                                                                       RW     9(1)                                                09 Serial Port 1 Flow Control                                                                    RW     F(1) 0=OFF, 1=ON                                    10 Serial Port 1 Redirection Type                                                                RW     9(1)                                                11 Serial Port 1 Destination Port                                                                RW     9(1)                                                12 Serial Port 2 Baud Rate                                                                       RW     9(5)                                                13 Serial Port 2 Data Bits                                                                       RW     9(1)                                                14 Serial Port 2 Parity                                                                          RW     X(1)                                                15 Serial Port 2 Stop Bits                                                                       RW     9(1)                                                16 Serial Port 2 Flow Control                                                                    RW     F(1) 0=OFF, 1=ON                                    17 Serial Port 2 Redirection Type                                                                RW     9(1)                                                18 Serial Port 2 Destination Port                                                                RW     9(1)                                                19 Serial Port 3 Baud Rate                                                                       RW     9(5)                                                20 Serial Port 3 Data Bits                                                                       RW     9(1)                                                21 Serial Port 3 Parity                                                                          RW     X(1)                                                22 Serial Port 3 Stop Bits                                                                       RW     9(1)                                                23 Serial Port 3 Flow Control                                                                    RW     F(1) 0=OFF, 1=ON                                    24 Serial Port 3 Redirection Type                                                                RW     9(1)                                                25 Serial Port 3 Destination Port                                                                RW     9(1)                                                26 Serial Port 4 Baud Rate                                                                       RW     9(5)                                                27 Serial Port 4 Data Bits                                                                       RW     9(1)                                                28 Serial Port 4 Parity                                                                          RW     X(1)                                                29 Serial Port 4 Stop Bits                                                                       RW     9(1)                                                30 Serial Port 4 Flow Control                                                                    RW     F(1) )=OFF, 1=ON                                    31 Serial Port 4 Redirection Type                                                                RW     9(1)                                                32 Serial Port 4 Destination Port                                                                RW     9(1)                                                ______________________________________                                    

During operation, the preferred terminal accumulates statistics relatingto the numbers of occurrences of various events. These statisticalcounts include the following, which are provided as an output inresponse to a GET STAT COUNTS command:

    ______________________________________                                        Statistical Counts -- File 07                                                 ______________________________________                                        23  "Attempted Card Reads" occurrence counter                                                                RO     9(2)                                    24  "Failed Card Reads" threshold                                                                            RW     9(2)                                    25  "Failed Card Reads" occurrence counter                                                                   RO     9(2)                                    26  "Attempted Embossed Data Reads" counter                                                                  RO     9(2)                                    27  "Failed Embossed Reads" threshold                                                                        RW     9(2)                                    28  "Failed Embossed Reads" occurrence counter                                                               RO     9(2)                                    39  "Chargeback Protection Inversion" threshold                                                              RW     9(2)                                        (occurs when the Chargeback Protection Flag is                                turned on and the Embossed Data Reader                                        Activated Flag is turned off)                                             40  "Chargeback Protection Inversion" counter                                                                RO     9(2)                                    43  "High Risk Violation" threshold                                                                          RW     9(2)                                    44  "High Risk Violation" occurrence counter                                                                 RO     9(2)                                    45  "Signature Not Captured" threshold                                                                       RW     9(2)                                    46  "Sign. Not Captured-No Sign Pad" counter                                                                 RO     9(2)                                    47  "Sign. Not Captured-Sign Pad Error" counter                                                              RO     9(2)                                    48  "Sign. Not Captured-No Sign Received"                                                                    RO     9(2)                                        counter                                                                   49  "Attempted Check Reads" occurrence counter                                                               RO     9(2)                                    50  "Failed Check Reads" threshold                                                                           RW     9(2)                                    51  "Failed Check Reads" occurrence counter                                                                  RO     9(2)                                    ______________________________________                                    

Transaction Guarantor Host Communication Packets

Under circumstances wherein the terminal 10 is utilized in conjunctionwith a chargeback protection system provided by a transaction guarantoror processor, as described in the referenced Data Card TerminalApplication, data packets comprising transaction data acquired by a POSelectronic cash register and payment data acquired with the preferredterminal 10 will be transmitted to the transaction processor. Chargebackprotection may be provided by the transaction guarantor under suchconditions as it deems prudent. For example, the transaction guarantormay deem that a transaction will only be chargeback protected if thetransaction includes a signature captured with an attached signaturepad. Other combinations of conditions may be utilized, as deemedprudent. As a specific example, consider that chargeback protection isonly allowed when a signature capture pad is attached. A typicalcommunication packet from the POS computer system, after acquisition ofthe transaction data from an electronic cash register, the preferredterminal 10, and a connected signature pad, appears as follows:

    ______________________________________                                        Field Name      Format     Remarks                                            ______________________________________                                        Record Descriptor Word                                                                        X(4)                                                          Terminal Type Code                                                                            9(2)       Always `77`                                        Field Separator 9(1)       Hex 22                                             Plan Number     9(2)                                                          Merchant Number 9(9)                                                          Terminal Serial Number                                                                        9(2)       Unique for                                                                    each register in                                                              any one                                                                       register                                           Filler          9(1)       Always `0`                                         Terminal Qual Code                                                                            9(5)                                                          Transaction Code                                                                              X(2)                                                          Entry Mode      9(1)       Transaction                                                                   entry method                                       Transaction Amount                                                                            9(8)       Implied                                                                       Decimal Point                                      Transaction Number                                                                            9(4)       Unique for                                                                    each                                                                          transaction in                                                                any one                                                                       register                                           Guarantee Flag  9(1)       Chargeback                                                                    guarantee status                                   0 = not guaranteed (no chargeback protection                                  no signature pad, no multi-reader)                                            1 = guaranteed with signature                                                 2 = guaranteed missing signature                                              3 = not guaranteed with signature                                             4 = not guaranteed missing signature                                          Receipt Header Option                                                                         9(1)       For receipt                                                                   reproduction                                                                  (0, 1, 2, 3, or 4)                                 Store Policy Line Option                                                                      9(1)       For receipt                                                                   reproduction                                                                  (0, 1, 2, or 3)                                    Greeting Message Line                                                                         9(2)       For receipt                                        Option                     reproduction                                                                  (00-50)                                            Track 1 or 2 magnetic stripe                                                                  X(Variable)                                                   data                                                                          OR - (for manual                                                              entry)                                                                        Card Account Number                                                                           9(Variable)                                                   Account Separator                                                                             9(1)       Always Hex 40                                                                 (space)                                            Card Expiration Date                                                                          9(4)       MMYY                                               Field Separators                                                                              9(1)       Always Hex 22                                      Digitized Signature                                                                           X(Variable)                                                                              passed from                                                                   multi-reader                                       Field Separator 9(1)       Always Hex 22                                      Authorization Code                                                                            X(8)                                                          Field Separator 9(1)       Always Hex 22                                      Transaction Date                                                                              9(4)       MMDD                                               ______________________________________                                    

From the foregoing, it will be understood that there has been describedapparatus and methods of operating an adjunct transaction terminal inconjunction with a system having a host computer (such as an in-storeprocessor) and an electronic cash register at the point of sale. Theadjunct transaction terminal 10 is connected for data communicationsbetween the host computer and the electronic cash register. The terminalis operative for acquiring adjunct transaction information independentlyof the electronic cash register, the adjunct transaction informationbeing related to a transaction being handled at the cash register.

In particular, the present invention is particularly suitable forconnection for communications in series between the host computer andthe electronic cash register, especially where the cash register onlyhas a limited number (perhaps only one) data communications port, whichport is designed to be connected only to the in-store or host computersystem. With the present invention, the single communications cable orwire provided from the host to the cash register at the POS mayadvantageously be utilized to connected the adjunct terminal 10, withthe cash register connected to one of the available serial ports 62,obviating the need to run additional communications cables or networkadapters to the POS cash register and cluttering the workspace at thepoint of sale.

As thus connected, the terminal 10 is operative to for receiving signalsbetween the host computer and the electronic cash register, determiningthe intended destination of the signals, responding to predeterminedsignals intended for the adjunct terminal by performing functionsassociated with the adjunct terminal, and forwarding remaining signalsto their intended destination. Only fairly minor programming changes arerequired for the host computer system to accommodate the presentinvention, and no programming changes at all may be required at the POSelectronic cash register. In some cases, however, where the electroniccash register includes a displaying means for displaying information,the terminal may, indirectly via the host, request the electronic cashregister to display a message on the displaying means associated with anaction to be take at the adjunct transaction terminal, such as "INSERTCREDIT CARD", or "INSERT CHECK", or "SIGN RECEIPT."

The preferred terminal, being adjunct to the POS cash register, collectsadjunct transaction data via a data collection means associated with theadjunct terminal, and provides the collected transaction data to thehost computer. In cases where the electronic cash register includes amanual data entry means such as a keyboard for receiving manuallyentered data associated with a transaction, the terminal is operativefor receiving manually entered transaction data from the electronic cashregister, obtaining the adjunct transaction information from a datacollection means associated with the adjunct transaction terminal,combining the manually entered transaction data with the adjuncttransaction information, and transmitting the combined manually enteredtransaction data and the adjunct transaction information to the hostcomputer.

The present invention has been described in relation to particularembodiments which are intended in all respects to be illustrative ratherthan restrictive. Alternative embodiments will become apparent to thoseskilled in the art to which the present invention pertains withoutdeparting from its spirit and scope. Accordingly, the scope of thepresent invention is defined by the appended claims rather than theforegoing description.

What is claimed is:
 1. A financial transaction processing system foracquiring transaction data associated with a financial transaction,comprising:a host computer; at least one electronic cash registeroperative for acquiring predetermined first transaction information inconnection with a financial transaction via a first transactioninformation obtaining means and for communicating said first transactioninformation to said host computer; a first communications link means forconnecting said host computer to said electronic cash register;at leastone multi-reader terminal independent of said electronic cash registerand for acquiring predetermined second transaction information inconnection with said financial transaction via at least one secondtransaction information obtaining means and for communicating saidsecond transaction information to said host computer; and a secondcommunications link connecting said multi-reader terminal to saidelectronic cash register, said multi-reader terminal being operative torespond to a predetermined set of signals from said host computer onsaid first communications link, and to pass signals intended for saidelectronic cash register to said electronic cash register via saidsecond communications link.
 2. The system of claim 1, wherein said firsttransaction information obtaining means comprises a keyboard associatedwith said electronic cash register for manual entry of transactioninformation.
 3. The system of claim 1, wherein said multi-readerterminal comprises a means for reading a magnetic stripe on a data card,means for reading an embossed region on a data card, or means forreading magnetic ink characters on a check.
 4. The system of claim 1,wherein said first transaction information comprises informationrelating to the purchase of goods or services by a customer, and whereinsaid second transaction information comprises information related to amedium of exchange presented by a customer to pay for said goods orservices.
 5. The system of claim 4, wherein said medium of exchangecomprises a credit card, a debit card, or a check.
 6. The system ofclaim 1, wherein said first communications link means comprises a serialdata communications link between said host computer and said electroniccash register, and wherein said multi-reader terminal is operative forconnection in between said electronic cash register and said hostcomputer.
 7. The system of claim 1, wherein said multi-reader terminalis operative to pass signals from said electronic cash register on saidsecond communications link to said host computer on said firstcommunications link.
 8. In a financial transaction system including ahost computer, a first transaction terminal for receiving firsttransaction information, and means for communicating said firsttransaction information from said first transaction terminal to saidhost computer, the improvement comprising:a second transaction terminalfor obtaining second transaction information connectable between saidhost computer and said first transaction terminal, comprising: firstconnecting means for connecting said host computer to said secondtransaction terminal; second connecting means for connecting said secondtransaction terminal to said first transaction terminal; means forreceiving host signals from said host computer; means responsive to saidhost signals received from said host computer for determining whethersaid host signals are intended for said first transaction terminal orfor said second transaction terminal; means responsive to adetermination that said host signals are intended for said firsttransaction terminal for transmitting said host signals to said firsttransaction terminal via said second connecting means; and meansresponsive to a determination that said host signals are intended forsaid second transaction terminal for responding to said host signals. 9.The improvement of claim 8, wherein said communicating means comprises aserial data communications port on said first transaction terminal, andwherein said first means comprises a serial data communication means forconnecting said host computer to said second transaction terminal, andwherein said second means comprises a serial data communication meansfor connecting said second transaction terminal to said firsttransaction terminal.
 10. The improvement of claim 8, wherein signalsprovided from said host computer are provided in a format whereinsignals intended for said first transaction terminal are embedded in acommunication message with indicia indicative that said signals areintended for said first transaction terminal, and wherein signalsintended for said second transaction terminal are embedded in acommunication message with indicia indicative that said signals areintended for said second transaction terminal.
 11. The improvement ofclaim 8, wherein said second transaction terminal includes a pluralityof serial data communications ports, wherein said determining meanscomprises a serial data communications controller, and wherein saidserial data communications controller is operative for controlling saidserial data communications ports in a plurality of selectiveconfigurations.
 12. The improvement of claim 11, wherein said serialdata communications controller is selectively operative to:1. Ignore allincoming data received on an incoming serial port;
 2. Accept allincoming data received on an incoming serial port as intended for saidsecond transaction terminal;
 3. Redirect all incoming data received onan incoming serial port, except for data recognizable as intended forsaid second transaction terminal, to an outgoing serial port; 4.Unconditionally redirecting data received on an incoming serial port toa selected outgoing serial port with no regard to the format andsubstance of the data; or
 5. Communicating with a peripheral deviceconnected to a selected serial port.
 13. The improvement of claim 12,wherein said peripheral device comprises a signature capture pad. 14.The improvement of claim 8, wherein said second transaction terminalcomprises a multi-reader terminal operative for obtaining financialtransaction information from a payment source.
 15. A method of operatingan adjunct transaction terminal in conjunction with a system having ahost computer and an electronic cash register, said adjunct transactionterminal being connected for data communications between said hostcomputer and said electronic cash register, comprising the stepsof:providing an adjunct terminal for acquiring adjunct transactioninformation independently of said electronic cash register, said adjuncttransaction information being related to a transaction being handled atsaid cash register; connecting said adjunct terminal for communicationsin series between said host computer and said electronic cash register;receiving signals between said host computer and said electronic cashregister; determining the intended destination of said signals;responding to predetermined signals intended for said adjunct terminalby performing functions associated with said adjunct terminal; andforwarding remaining signals to their intended destination.
 16. Themethod of claim 15, wherein said step of responding to predeterminedsignals comprises the step of collecting transaction data via a datacollection means associated with said adjunct transaction terminal, andproviding collected transaction data to said host computer as saidadjunct transaction information.
 17. The method of claim 16, whereinsaid data collection means comprises one or more of a magnetic stripereader for reading a magnetic stripe on a credit card, an embossedcharacter reader for reading an embossed character region on a creditcard, a magnetic ink character recognition (MICR) reader, a personalidentification number (PIN) entry pad, or a signature capture pad. 18.The method of claim 15, wherein said electronic cash register includes adisplay for displaying information, and wherein the step of respondingcomprises requesting the electronic cash register to display a messageon the display associated with an action to be taken at said adjuncttransaction terminal.
 19. The method of claim 15, wherein saidelectronic cash register includes a manual data entry means forreceiving manually entered data associated with a transaction, andwherein said step of responding comprises:receiving manually enteredtransaction data from the electronic cash register; obtaining theadjunct transaction information from a data collection means associatedwith the adjunct transaction terminal; combining the manually enteredtransaction data with the adjunct transaction information; transmittingthe combined manually entered transaction data and the adjuncttransaction information to the host computer.
 20. The system of claim 1,wherein said multi-reader terminal comprises a plurality of data recordreaders for acquiring predetermined second transaction information, saidplurality of data record readers being selected from the groupincluding: a data card magnetic stripe reader, a data card embossed cardreaders, and a magnetic ink character recognition (MICR) check reader.21. The system of claim 1, wherein said multi-reader terminalcomprises:a plurality of serial data communications ports, a first ofsaid ports connecting said multi-reader terminal to said electronic cashregister, a second of said ports connecting said multi-reader terminalto said host computer; and a serial data communications controller, saidserial data communications controller being operative for controllingsaid plurality of serial data communications ports in a plurality ofselective configurations.
 22. The system of claim 21, wherein saidserial data communications controller is selectively operative to:1.Ignore all incoming data received on an incoming serial port;
 2. Acceptall incoming data received on an incoming serial port as intended forsaid multi-reader terminal;
 3. Redirect all incoming data received on anincoming serial port, except for data recognizable as intended for saidmulti-reader terminal, to an outgoing serial port;
 4. Unconditionallyredirect data received on an incoming serial port to a selected outgoingserial port with no regard to the format and substance of the data; or5. Communicate with a peripheral device connected to a selected serialport.
 23. The system of claim 22, wherein said peripheral devicecomprises a signature capture pad.
 24. The improvement of claim 14,wherein said multi-reader terminal comprises a data card magnetic stripereader, an embossed card reader, and a magnetic ink characterrecognition (MICR) check reader, and wherein said payment sourcecomprises a data card or a check.
 25. A financial transaction processingsystem for acquiring transaction data associated with a financialtransaction, comprising:a host computer; at least one electronic cashregister operative for acquiring predetermined first transactioninformation in connection with a financial transaction via a firsttransaction information obtaining device and for communicating saidfirst transaction information to said host computer; a firstcommunications link connecting said host computer to said electroniccash register; at least one multi-reader terminal independent of saidelectronic cash register and for acquiring predetermined secondtransaction information in connection with said financial transactionvia at least one second transaction information obtaining device and forcommunicating said second transaction information to said host computer;and a second communications link connecting said multi-reader terminalto said electronic cash register, said multi-reader terminal beingoperative to respond to a predetermined set of signals from said hostcomputer on said first communications link, and to pass signals intendedfor said electronic cash register to said electronic cash register viasaid second communications link.
 26. The system of claim 25, whereinsaid first transaction information obtaining device comprises a keyboardassociated with said electronic cash register for manual entry of saidfirst transaction information.
 27. The system of claim 25, wherein saidsecond transaction information obtaining device comprises a magneticstripe reader for reading a magnetic stripe on a data card, an embosseddata reader for reading an embossed region on a data card, or a magneticink character reader for reading magnetic ink characters on a check. 28.The system of claim 25, wherein said first transaction informationcomprises information relating to the purchase of goods or services by acustomer, and wherein said second transaction information comprisesinformation related to a medium of exchange presented by a customer topay for said goods or services.
 29. The system of claim 28, wherein saidmedium of exchange comprises a credit card, a debit card, or a check.30. The system of claim 25, wherein said first communications linkcomprises a serial data communications link between said host computerand said electronic cash register, and wherein said multi-readerterminal is operative for connection in between said electronic cashregister and said host computer.
 31. The system of claim 25, whereinsaid multi-reader terminal is operative to pass signals from saidelectronic cash register on said second communications link to said hostcomputer on said first communications link.
 32. The system of claim 25,wherein said multi-reader terminal further comprises:a plurality ofserial data communications ports, a first of said serial portsconnecting said multi-reader terminal to said electronic cash register,a second of said serial ports connecting said multi-reader terminal tosaid host computer; and a serial data communications controller, saidserial data communications controller being operative for controllingsaid serial data communications ports in a plurality of selectiveconfigurations.
 33. The system of claim 32, wherein said serial datacommunications controller is selectively operative to:1. Ignore allincoming data received on an incoming serial port;
 2. Accept allincoming data received on an incoming serial port as intended for saidmulti-reader terminal;
 3. Redirect all incoming data received on anincoming serial port, except for data recognizable as intended for saidmulti-reader terminal, to an outgoing serial port;
 4. Unconditionallyredirect data received on an incoming serial port to a selected outgoingserial port with no regard to the format and substance of the data; or5. Communicate with a peripheral device connected to a selected serialport.
 34. The system of claim 33, wherein said peripheral devicecomprises a signature capture pad.
 35. In a financial transaction systemincluding a host computer, a first transaction terminal for receivingfirst transaction information, said first transaction terminal includinga communications port for communicating said first transactioninformation from said first transaction terminal to said host computer,the improvement comprising:a second transaction terminal connectablebetween said host computer and said first transaction terminal forobtaining second transaction information, said second transactionterminal comprising: a first communications port for connecting saidhost computer to said second transaction terminal; a secondcommunications port for connecting said second transaction terminal tosaid first transaction terminal communications port; and controlcircuitry responsive to host signals received from said host computerfor determining whether said host signals are intended for said firsttransaction terminal or for said second transaction terminal; saidcontrol circuitry responsive to a determination that said host signalsare intended for said first transaction terminal for transmitting saidhost signals to said first transaction terminal via said secondcommunications port, and responsive to a determination that said hostsignals are intended for said second transaction terminal for respondingto said host signals.
 36. The improvement of claim 35, wherein saidfirst transaction terminal communications port comprises a serial datacommunications port, and wherein said first communications portcomprises a serial data communications port for connecting said hostcomputer to said second transaction terminal, and wherein said secondcommunications port comprises a serial data communications port forconnecting said second transaction terminal to said first transactionterminal.
 37. The improvement of claim 36, wherein said secondtransaction terminal further includes a serial data communicationscontroller, said serial data communications controller being operativefor controlling said serial ports in a plurality of selectiveconfigurations.
 38. The improvement of claim 37, wherein said serialdata communications controller is selectively operative to:1. Ignore allincoming data received on an incoming serial port;
 2. Accept allincoming data received on an incoming serial port as intended for saidsecond transaction terminal;
 3. Redirect all incoming data received onan incoming serial port, except for data recognizable as intended forsaid second transaction terminal, to an outgoing serial port; 4.Unconditionally redirect data received on an incoming serial port to aselected outgoing serial port with no regard to the format and substanceof the data; or
 5. Communicate with a peripheral device connected to aselected serial port.
 39. The improvement of claim 38, wherein saidperipheral device comprises a signature capture pad.
 40. The improvementof claim 35, wherein signals provided from said host computer areprovided in a format wherein signals intended for said first transactionterminal are embedded in a communication message with indicia indicativethat said signals are intended for said first transaction terminal, andwherein signals intended for said second transaction terminal areembedded in a communication message with indicia indicative that saidsignals are intended for said second transaction terminal.
 41. Theimprovement of claim 35, wherein said second transaction terminalcomprises a multi-reader operative for obtaining said second transactioninformation from a payment source.
 42. The improvement of claim 41,wherein said multi-reader comprises a data card magnetic stripe reader,an embossed card reader, and a magnetic ink character recognition (MICR)check reader, and wherein said payment source comprises a data card or acheck.